Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Babbage Formal Spec #2479

Closed
JaredCorduan opened this issue Sep 15, 2021 · 7 comments
Closed

Babbage Formal Spec #2479

JaredCorduan opened this issue Sep 15, 2021 · 7 comments

Comments

@JaredCorduan
Copy link
Contributor

JaredCorduan commented Sep 15, 2021

We need a Babbage formal spec, covering:

  • Protocol

    • a single VRF check
    • removal of protocol params: d and extra entropy
    • no overlay schedule / OBFT
  • Ledger

@WhatisRT
Copy link
Contributor

Also 2-phase validation for... 1-phase scripts. That naming scheme aged well^^

@michaelpj
Copy link
Contributor

  • Compression
  • Inline datums

@yihuang
Copy link

yihuang commented Dec 1, 2021

Will babel fee supported in this era? And the multi-tier gas price system described by recent blog post?

@WhatisRT
Copy link
Contributor

WhatisRT commented Dec 1, 2021

The list at the top is the full list of what's planned. So probably not.

@mark-stopka
Copy link

Will babel fee supported in this era? And the multi-tier gas price system described by recent blog post?

Babel fees are certainly something requiring much more community dialogue, don't you think? How would you value those native tokens relative to ADA for instance?

@yihuang
Copy link

yihuang commented Dec 6, 2021

Will babel fee supported in this era? And the multi-tier gas price system described by recent blog post?

Babel fees are certainly something requiring much more community dialogue, don't you think? How would you value those native tokens relative to ADA for instance?

The liquidity market is done off-chain, what's needed on-chain is to support the grouped transactions, several invalid transactions (might contain negative ada output) can be valid after grouped as a bundle. Like a cheap way to do an atomic swap.

@WhatisRT
Copy link
Contributor

WhatisRT commented Dec 6, 2021

Yes, so while it's clear what kind of changes would enable Babel fees, actually implementing those would require quite big changes to the ledger (and maybe even other parts of the system).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants