HackMD
    • Sharing Link copied
    • /edit
    • View mode
      • Edit mode
      • View mode
      • Book mode
      • Slide mode
      Edit mode View mode Book mode Slide mode
    • Note Permission
    • Read
      • Only me
      • Signed-in users
      • Everyone
      Only me Signed-in users Everyone
    • Write
      • Only me
      • Signed-in users
      • Everyone
      Only me Signed-in users Everyone
    • More (Comment, Invitee)
    • Publishing
    • Commenting Enable
      Disabled Forbidden Owners Signed-in users Everyone
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Invitee
    • No invitee
    • Options
    • Versions and GitHub Sync
    • Transfer ownership
    • Delete this note
    • Template
    • Save as template
    • Insert from template
    • Export
    • Google Drive Export to Google Drive
    • Gist
    • Import
    • Google Drive Import from Google Drive
    • Gist
    • Clipboard
    • Download
    • Markdown
    • HTML
    • Raw HTML
Menu Sharing Help
Menu
Options
Versions and GitHub Sync Transfer ownership Delete this note
Export
Google Drive Export to Google Drive Gist
Import
Google Drive Import from Google Drive Gist Clipboard
Download
Markdown HTML Raw HTML
Back
Sharing
Sharing Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
More (Comment, Invitee)
Publishing
More (Comment, Invitee)
Commenting Enable
Disabled Forbidden Owners Signed-in users Everyone
Permission
Owners
  • Forbidden
  • Owners
  • Signed-in users
  • Everyone
Invitee
No invitee
   owned this note    owned this note      
Published Linked with GitHub
Like BookmarkBookmarked
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
# Simple shard data fee market The following is a simple market for shard data that uses an agreed upon contract on eth1 (or the eth1 shard) for coordination. It relies upon some eth2 system level accesses including access to: the validator set, recent slot shard data roots, and recent shard proposer indices. ## Contract interface and storage ### Types * `BLSPubkey: bytes48` * `BLSSignature: bytes96` * `Eth1Addr: bytes20` * `ValidatorIndex: uint64` * `Epoch: uint64` * `Slot: uint64` * `Root: bytes32` * `Bounty: {owner: Eth1Addr, data_root: Root, value: Wei, expiration: Slot, consumed: Bool, withdrawn: Bool}` ### Storage * `validator_addrs: map[ValidatorIndex -> ETH1Addr]` * `bounties: list[Bounty]` ### Functions #### `register_validator` *Registers an eth1 address for a given validator index* `register_validator(index: ValidatorIndex, eth1_addr: ETH1Addr, registration_proof: BLSSignature)` * `assert num_validators() > index` * let `validator = get_validator_by_index(index)` * let `pubkey = validator.pubkey` * Check that `registration_proof` is a valid BLS signature for `pubkey` over `eth1_addr` (probably with some signature domain) * If invalid: exit * set `validator_addrs[index] = eth1_addr` #### `post_bounty` *Posts a bounty for `data_root` that expires at `expiration` slot. Sets an eth1 `owner` with the ability to withdraw if expiration is breached* `post_bounty(owner: Eth1Addr, data_root: Root, expiration: Slot) payable` * _maybe_ `assert msg.value > 0` * Create `bounty = Bounty(owner, data_root, msg.value, expiration, False, False)` * Append `bounty` to `bounties` #### `claim_bounty` *Allows for `bounty` define by `bounty_index` to be claimed if `bounty.data_root` is the shard block root for `shard` at `shard_slot`. Bounties are paid to the proposer of the shard block and proposers must be pre-registered in `validator_addrs`* `claim_bounty(bounty_index: uint64, shard: Shard, shard_slot: Slot)` * `assert len(bounties) > bounty_index` * let `bounty = bounties[bounty_index]` * let `proposer_index = get_shard_proposer_index_at_slot(shard, shard_slot)` * `assert validator_addrs[proposer_index] != 0x00` * `assert not bounty.consumed` * `assert timestamp_to_slot(block.timestamp) < bounty.expiration` * `assert get_shard_root_at_slot(shard, shard_slot) == bounty.data_root` * set `bounty.consumed = True` * send `bounty.value` to `validator_addrs[proposer_index]` #### `withdraw_bounty` *Allows for a `bounty` to be withdrawn if it is expired and not yet consumed. Withdrawals go to `eth1.owner`.* `withdraw_bounty(bounty_index: uint64)` * `assert len(bounties) > bounty_index` * let `bounty = bounties[bounty_index]` * `assert not bounty.consumed` * `assert timestamp_to_slot(block.timestamp) >= bounty.expiration` * `assert not bounty.withdrawn` * set `bounty.withdrawn = True` * send `bounty.value` to `bounty.owner` ## Things to consider ### Expiration reform A `bounty` might want to separate out `on_chain_expiration` vs `claim_expiration`. The former being the slot by which the data should make it on chain, and the latter being how long the validator can go to claim the bounty. A user might want an aggressive `on_chain_expiration` to see data get on chain quickly, but the validator might want some breathing room to claim the bounty with a farther out `claim_expiration`. ### data bounties for `data_root` embedded shard block data It would probably be valuable to be able to post data bounties that don't have the be the top level root in a shard block. This would require a merkle proof scheme be able to be submitted to `claim_bounty` rather than the assumption it's the top level root on the shard. One thing is we need to ensure that the `data_root` is not just trivially included as a leaf. ### Fewer on chain TXs Can we remove `post_bounty` as an on-chain TX and instead just attach it to the `data_root` in the mempool? Maybe a cryptoeconomic commitment (slashing) or some sort of payment/state channel. The challenge with open-ended off-chain payments is that you can self-claim all the funds and so front-run everyone whom you claimed to pay. If we can't remove `post_bounty`, then the getting data on chain naively requires at least a 2 slot latency. Another thing to consider is slot staggering of execution shard(s) and data shards. That is, within a single slot, the bounty is posted on the execution shard then later in the slot, the data shard block is produced.

Import from clipboard

Advanced permission required

Your current role can only read. Ask the system administrator to acquire write and comment permission.

This team is disabled

Sorry, this team is disabled. You can't edit this note.

This note is locked

Sorry, only owner can edit this note.

Reach the limit

Sorry, you've reached the max length this note can be.
Please reduce the content or divide it to more notes, thank you!

Import from Gist

Import from Snippet

or

Export to Snippet

Are you sure?

Do you really want to delete this note?
All users will lost their connection.

Create a note from template

Create a note from template

Oops...
This template has been removed or transferred.


Upgrade

All
  • All
  • Team
No template.

Create a template


Upgrade

Delete template

Do you really want to delete this template?

This page need refresh

You have an incompatible client version.
Refresh to update.
New version available!
See releases notes here
Refresh to enjoy new features.
Your user state has changed.
Refresh to load new user state.

Sign in

Sign in via SAML

or

Sign in via GitHub

Help

  • English
  • 中文
  • 日本語

Documents

Tutorials

Book Mode Tutorial

Slide Example

YAML Metadata

Resources

Releases

Blog

Policy

Terms

Privacy

Cheatsheet

Syntax Example Reference
# Header Header 基本排版
- Unordered List
  • Unordered List
1. Ordered List
  1. Ordered List
- [ ] Todo List
  • Todo List
> Blockquote
Blockquote
**Bold font** Bold font
*Italics font* Italics font
~~Strikethrough~~ Strikethrough
19^th^ 19th
H~2~O H2O
++Inserted text++ Inserted text
==Marked text== Marked text
[link text](https:// "title") Link
![image alt](https:// "title") Image
`Code` Code 在筆記中貼入程式碼
```javascript
var i = 0;
```
var i = 0;
:smile: :smile: Emoji list
{%youtube youtube_id %} Externals
$L^aT_eX$ LaTeX
:::info
This is a alert area.
:::

This is a alert area.

Versions

Versions and GitHub Sync

Sign in to link this note to GitHub Learn more
This note is not linked with GitHub Learn more
 
Add badge Pull Push GitHub Link Settings
Upgrade now

Version named by    

More Less
  • Edit
  • Delete

Note content is identical to the latest version.
Compare with
    Choose a version
    No search result
    Version not found

Feedback

Submission failed, please try again

Thanks for your support.

On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

Please give us some advice and help us improve HackMD.

 

Thanks for your feedback

Remove version name

Do you want to remove this version name and description?

Transfer ownership

Transfer to
    Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

      Link with GitHub

      Please authorize HackMD on GitHub

      Please sign in to GitHub and install the HackMD app on your GitHub repo. Learn more

       Sign in to GitHub

      HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.

      Push the note to GitHub Push to GitHub Pull a file from GitHub

        Authorize again
       

      Choose which file to push to

      Select repo
      Refresh Authorize more repos
      Select branch
      Select file
      Select branch
      Choose version(s) to push
      • Save a new version and push
      • Choose from existing versions
      Available push count

      Upgrade

      Pull from GitHub

       
      File from GitHub
      File from HackMD

      GitHub Link Settings

      File linked

      Linked by
      File path
      Last synced branch
      Available push count

      Upgrade

      Danger Zone

      Unlink
      You will no longer receive notification when GitHub file changes after unlink.

      Syncing

      Push failed

      Push successfully