Create a Coffer
Open the app and start the create wizard. It has four steps, and deploying signs one transaction from your wallet at the end.
Step 1, the guide
Section titled “Step 1, the guide”Create Your First Coffer shows the checklist covered in Before you create a Coffer. Press Begin when everything on it is ready.
Step 2, predict the address
Section titled “Step 2, predict the address”Point your validator at a Coffer asks for two things, the owner address and your Validator public key, 48 bytes as 96 hex characters. From them the app predicts your Coffer’s address before it exists, the factory deploys deterministically, so the same owner and key always produce the same address.
The prediction appears as Your Coffer address with a Copy button, and the line under it says what to do with it, “Use this as the withdrawal address when generating keys with ethstaker-deposit-cli (0x02 compounding).”
Step 3, configure terms
Section titled “Step 3, configure terms”Configure terms collects the offer. The app notes that most of these you can adjust later.
| Field | Unit | Bounds |
|---|---|---|
| Amount (ETH) | ETH | 32–2048 ETH, your validator’s starting balance |
| Interest rate | % / yr | above zero, at most 100 percent |
| Min duration | days | above zero, at most the max duration |
| Max duration | days | at most 50 years |
| Issue size buffer | bps | under 10000, where 100 bps is 1 percent |
| Minimum amount to accept | ETH | at most the buffer scaled starting balance |
The amount is the balance your validator will hold, and the contract derives your opening issue size from it at the buffer discount. Report it honestly, holders check it against the beacon chain before buying. The buffer is your reserve against penalties, How a bond works explains what it protects.
Step 4, review and deploy
Section titled “Step 4, review and deploy”Review & deploy lists every value, Owner, Validator key, Coffer address, Starting balance, Interest rate, Duration range, Issue Size Buffer and Min amount. Check the owner. If it is not your connected wallet, the app warns, “This Coffer would be owned by your connected wallet, not the owner you entered, and would deploy to a different address than the one predicted. Go back and set the owner to your connected wallet.”
Deploy, sign the transaction, and the Coffer exists at the predicted address.
After the deploy
Section titled “After the deploy”Your new Coffer reads Unknown in red until a deposit for your validator is found, which is normal for a Coffer that was just deployed. Its mark is red too, because the Coffer already has an issue size and the stake is not on the beacon chain yet. Once the deposit is found with credentials that point to your Coffer the pill reads Pending, and once the validator is on the beacon chain with its stake the mark turns green. A deposit with 0x00 credentials reads Credentials, and one that names another address reads Mismatch. Until then Browse does not list the Coffer, and your portfolio always does. If you deposited before deploying, the status moves on its own within hours. If not, the lifecycle screen’s open rung, “Set your withdrawal credentials”, walks you through the deposit, Point your validator at the Coffer is the same ground in these docs, and Coffer lifecycle and statuses explains every state.