NOTE: This document is a DRAFT. Expect it to change often as it is WORK IN PROGRESS DEPRECATED. A new version will be published at some point.
| Table of Contents | ||
|---|---|---|
|
...
- how to do weighted multi-signature
- notification on block finalization (check with Michael Birch (Unlicensed) & Former user (Deleted))
- do Should we need have a shard tree or a shard DAGDAG in a future version?
- how to roll-back cross-shard transfers when something goes wrong during the transfer?
- how to mount an existing shard?
- How to unmount a shard without destroying it?
- Why not register all the wallets in a public WalletRegistry?
- Do we sign the "approved" contracts used for REV?
- How to avoid the situation when the validators move their stakes out of the child shard while still holding their validator status?
- How does interaction with PoS contract happens at bonding/unbonding
- how to update K in order to keep the K/N ratio the same as validators bond/unbond. Should we keep the ratio in the config and re-compute K each time?
...
Depository.Deposit API | ||
|---|---|---|
| transferToChild | Purse → PublicKey → Name | destroys the content of the purse and returns the name of a new wallet located in the child-shard, minus fees. The new wallet contains tokens . The wallet can be used by the owner of the corresponding private-key The returned name is a wallet registered in the parent child shard |
Depository.Withdrawer API | ||
|---|---|---|
| withdraw | Amount → Purse | destroys the content of the purse and returns the name of a new purse located in the parent shard, minus fees. The new purse is sprouted from the Depository and its value + fees is removed from the Depository. The returned name is a wallet registered in the parent shard |
...