Repository navigation
Conversation
7f1bbf4 to
fed6304
Compare
valthon
changed the title
Clarify daemon startup, verification artifacts, timing and recovery for automatic syndication underwriting. Document production seed capital from pre-launch syndication through the epoch-zero import and funding-account link, followed by liquid shadow-LIQ transfers to every batch operator after WIRE starts. Keep launch accounts, allocations and caps as placeholders and provide read-only acceptance checks for the funding handoff.
fed6304 to
0ffed86
Compare
heifner
left a comment
heifner
left a comment
There was a problem hiding this comment.
Checked the playbook against wire-sysio master, wire-tools-ts master and the outposts' next. The harness behaviour (sync-only operator nodes under --external-outpost-config, full args in start.sh / run), the plugin timings and halt message, the retention limits and the depot actions named here all match the code. Two things to fix, inline.
| clio -u "$WIRE_RPC" get table sysio.liq "<FUNDER_WIRE_ACCOUNT>" accounts | ||
| clio -u "$WIRE_RPC" get table sysio.liq "<BATCH_OPERATOR_WIRE_ACCOUNT>" accounts |
There was a problem hiding this comment.
These fail as written. clio get table takes two positionals (account table); the scope goes in -S:
$ clio get table sysio.liq someacct accounts
ERROR: table: The following argument was not expected: accounts
sysio.liq balances are scoped by holder, so:
| clio -u "$WIRE_RPC" get table sysio.liq "<FUNDER_WIRE_ACCOUNT>" accounts | |
| clio -u "$WIRE_RPC" get table sysio.liq "<BATCH_OPERATOR_WIRE_ACCOUNT>" accounts | |
| clio -u "$WIRE_RPC" get table sysio.liq accounts -S "<FUNDER_WIRE_ACCOUNT>" | |
| clio -u "$WIRE_RPC" get table sysio.liq accounts -S "<BATCH_OPERATOR_WIRE_ACCOUNT>" |
The four commands under "Existing testnet" (the sysio.bond / sysio.synd / sysio.liq "$OPERATOR" block) have the same three-positional shape on master. This section sends readers to those checks, so they are worth fixing in the same pass.
|
|
||
| Use the on-chain WIRE account names from the launch roster | ||
| ([`wire-opreg-bootstrap.json`](outpost/README.md)), rather than keystore labels | ||
| such as `batchop.a`. Inventory and exposure caps are separate: an account can hold |
There was a problem hiding this comment.
This and the resource wording will collide with #186, which also edits this file (a trial merge of the two heads conflicts in the opening sentence and the troubleshooting paragraph).
- Bootstrap Without a Tier-1 Node Owner #186 has
sysiocreate each operator account under its label, sobatchop.abecomes the on-chain name. Dropping the example here ("use the account names from the launch roster") stays true either way. - Bootstrap Without a Tier-1 Node Owner #186, with wire-sysio#762, removes the bond-row RAM grant. The new text still asks for operator resources in pre-launch step 3 ("Provision each operator's resources"), in launch acceptance ("resources and signing configuration") and in troubleshooting ("insufficient RAM"). Those are correct on master today; whichever PR lands second needs to sweep them.
Document automatic underwriting setup and the production launch funding handoff. The funding party syndicates real LIQ before launch, the epoch-zero import credits or parks that position, and the funder transfers liquid shadow LIQ to each batch operator shortly after WIRE goes online.
The production section includes placeholders for accounts, external identities, per-operator allocations, exposure caps, and the funding owner/completion target. It covers account linking, keeping relays operational during funding, a
sysio.liq::transfertemplate, read-only acceptance checks, reconciliation of liquid balances and unclaimed bonds, and requests that approach the outpost retention window.The playbook also clarifies external-outpost startup, verification artifacts and RPC sources, normal scheduling, INVALID-bond recovery, and draining pending envelopes before replacing an outpost deployment.