Gardens
A Garden lets users stake one asset and earn partner rewards.
#How a Garden differs
Garden accounting follows the same finite, pre-funded model as a Greenhouse. The important difference is that the partner reward token must be different from the staking token. The constructor rejects a same-asset program.
#Partner funding
The program manager approves the reward amount first. The scheduling call then transfers that amount into the program and sets its timing atomically. Users should verify the funded amount, token contract, duration, start and finish times, and any external token restrictions before staking.
#User actions
Users stake the supported asset, accrue a proportional share of the partner token, claim available rewards, and withdraw principal. New stake can be paused, but normal and emergency principal exits remain in the contract.
#Sequential schedule blocker
Garden inherits Greenhouse scheduling. Starting a later program on the same instance can overwrite timing before the prior program's final reward interval is checkpointed, which can erase that uncheckpointed user reward.
#Partner token risk
A Garden adds the risks of an external reward token. The token may lose value, pause transfers, charge fees, blacklist accounts, or behave unexpectedly. WeedSwap cannot guarantee a partner token’s market, issuer, or transfer behavior.