Terms and what can change
You set the terms at creation and can change most of them later, from your Coffer’s own view. Every bond keeps the terms it was bought with, so a change only shapes the bonds you sell from then on. The bounds for each field are on Create a Coffer, this page is about what moves, when, and what a move does.
Open your Coffer, and in the Owner Controls card, under Issuance, press Change Terms. The panel opens with your current terms filled in, seven fields from top to bottom. The Active switch comes first, then Interest rate in percent per year, Issue size in ETH and Issue size buffer in bps with its percent shown beside it. Min duration and Max duration follow in days, and Minimum amount to accept in ETH closes the list. Edit what you want, leave the rest, and press Confirm. Everything you changed goes out as one transaction, and a field you did not touch is never sent. The button stays off until something has changed and no field shows an error, and Cancel closes the panel with nothing sent.
What is locked while bonds are outstanding
Section titled “What is locked while bonds are outstanding”While any bond is outstanding, four of the seven fields can move only in your holders’ favour. The panel says so at the top, “This coffer has outstanding bonds, so some parameters are locked or can only move in your holders’ favour until all bonds mature.” No field is greyed out. The wrong direction shows an error line under the field and Confirm stays off.
| Field | With no bond outstanding | While bonds are outstanding | The error line |
|---|---|---|---|
| Active | on or off | on or off | none |
| Interest rate | up or down | down only | “Cannot increase interest rate with outstanding bonds.” |
| Issue size | up or down | down only | “Can only decrease while bonds are outstanding” |
| Issue size buffer | up or down | up only | “Can only increase while bonds are outstanding” |
| Min duration | up or down | up or down | none |
| Max duration | up or down | down or unchanged | “Cannot increase while bonds are outstanding” |
| Minimum amount to accept | up or down | up or down | none |
Each locked move would let you shift the numbers against holders who already bought. A higher rate or a bigger issue size promises more against the same stake. A longer maximum widens the window for the penalties the buffer was sized against, and a smaller buffer thins that reserve. The contract allows only the moves that leave those holders as well off or better. A bond counts as outstanding while its maturity value is not zero, a matured bond nobody has redeemed included, so the locks lift only when the last bond is settled. Until the app has read the count from the chain it treats bonds as outstanding. The minimum duration is your own notice period and moves freely either way, size it against your monitoring habit as the Default page says.
The bounds
Section titled “The bounds”A change keeps to the bounds of creation. The rate is above zero and at most 100 percent, the app says “Interest rate must be greater than 0%.” or “Interest rate cannot exceed 100%.” Durations are whole positive days, the maximum at most 50 years and at least the minimum, “Duration exceeds the maximum (50 years).” and “Must be ≥ min duration”. The buffer stays below 10000 bps, “Issue size buffer must be below 10,000 bps (100%).” Both amounts are above zero. The issue size is at least the minimum amount to accept, the line “Must be at least the minimum amount to accept” with the figure in ETH after it, and a lower minimum in the same edit relaxes it. One bound from creation does not return, the minimum amount is no longer capped by the buffer scaled starting balance.
What a change does not do
Section titled “What a change does not do”A change never reaches a bond that exists. Each bond froze its rate, its duration and its maturity value when it was bought, so lowering the rate or shortening the range changes nothing for them. A buffer change moves no capacity on its own, the buffer scales the issue size only at creation and when you add funds to the beacon chain, so raising it afterwards changes what holders read, not what you can issue. Changing the issue size sets the number outright, it is not a step up or down from the current one. Terms can be changed while your Coffer is in default, but no bond sells until you have cleared the default, see Default.
The version
Section titled “The version”Your Coffer counts the changes that touch holder protections. A change of the rate, the durations, the issue size or the buffer bumps the count, and so do a withdrawal from the contract’s own balance, Withdraw · Execution, and clearing a default. The minimum amount and the Active switch leave it alone. A purchase carries the count the buyer saw when the form opened, and a change in between makes that purchase fail with “Coffer terms have changed since you opened this form. Please close and reopen.” That is what stops a change from landing under a buyer’s feet, and the app never shows the number itself.
Closing your Coffer to new bonds
Section titled “Closing your Coffer to new bonds”Switch Active off in the same panel and press Confirm. From then on no bond sells, visitors no longer see the Buy Bond card, a purchase already in flight fails, and the status badge on your terms card reads Closed in place of Active. The Browse list keeps showing the lifecycle status, since closing is your own switch and does not outrank a real problem. Existing bonds run on unchanged, the count does not move, and switching Active back on reopens sales the same way.
After you confirm
Section titled “After you confirm”The button reads Confirm in wallet while your wallet asks, Processing… while the transaction is in flight and Syncing… while the app catches up. The toast “Terms updated” appears at the receipt, and the panel closes on its own once the app shows the new terms, usually a few seconds later. If that takes too long, the panel says “Transaction confirmed but server sync timed out. Please refresh.” and your change is on chain all the same. The terms card then shows the new values, and holders see them the next time their view refreshes.