The first version of , a governance explorer and discourse forum for
#Tezos
is finally live!
For background on the project and where we hope to take things, check out our introductory blog post here:
We've been ramping up the
@TQTezos
team throughout 2019 and will be expanding further over the next few months!
Looking for:
- Sr. UX/UI designer
- Frontend developers
- Smart contract engineers
- PM, Marketing roles
If you're interested in/open to NYC, DMs open!
What wonderful, sunny summer day. Perfect for a
@tezos
protocol proposal injection. Tezos Community, sorry for the wait but Babylon has just been injected!
Babylon 2.0 (i.e. PsBABY5HQ):
Supermajority โ
Quorum โ
Next:
Testing Period (~ 3 weeks)
Promotion Period (~3 weeks)
If accepted, upgrade to Babylon 2.0 is slated to occur
~ October 16 EST
Tezos baker "Staked" /tz1RCFbB9GpALpsZtu6J58sb74dm8qe6XBzv voted "yay" with 696 rolls on
#Tezos
proposal "Babylon 5"
Vote status is 100.00% yay/0.00% nay, and quorum has been reached for the exploration phase.
Update from
@LigoLang
about plasma (i.e. Marigold) on Tezos
They're implementing first as smart contracts and want to explore adding plasma functionality to the base layer via protocol amendment
Blockpower (842 rolls) voted Yay on
#Tezos
proposal Babylon 2.0
Vote status is 91.59% Yay / 8.41% Nay and quorum has been reached for the promotion phase:
Brace yourselves...
๐ซ๐ซ๐ซ
Because exciting
@tezos
proposal(s) will be injected (sometime) during week 29!
๐ซ๐ซ๐ซ
Make sure you stay up-to-date by reading all the relevant articles (this list is updated regularly):
Babylon is a big step up from Athens, which just changed some constants. And it's the work of 3 teams:
@LabosNomades
,
@CryptiumLabs
, and Marigold (team also behind
@LigoLang
)
What's in it?
"The purpose of on-chain governance is often misconstrued as an attempt to make protocol rules easier to change. Its strength actually resides in its ability to programmatically define which rules are immutable, and which can be changed under which conditions."
For those looking to follow along with Tezos happenings, The Baking Sheet now has a new home.
New post out today has all of the awesome stuff that happened this week
HOT OFF THE OVEN -- We are excited to inform the community that Tezos Commons will be taking over the Baking Sheet Newsletter from
@camlCaseTech
. Stay up to date with news across the entire Tezos Ecosystem.
Check out and subscribe below:
This is a great answer when people ask why they should care about
@tezos
and what its meme is:
Tezos is open, self-upgrading economic infrastructure for the entire world
Protocol: Consensus
- In advance of the upcoming "B" proposal, the NL consensus team is finishing analysis of Emmy+ (new consensus algo) and tweaking protocol constants
- The Tezos-Tendermint proof-of-concept is nearly ready (!)
This slide by
@LabosNomades
sums up their view on smart contracts:
- SCs represent money/value (sometimes a lot)
- SCs are long-lived & unforgiving (can't easily update in case of bug without centralization)
- infinite possible input values, so testing can't be exhaustive
Cryptography
- Binding to ZCash Sapling library is almost done and they are preparing it for a future protocol proposal (!)
- Refreshing the HACL* cryptographic library to provide a verified implementation of P-256 on top of Ed25519
We are very excited to announce that we have received a grant from the
@TezosFoundation
to develop a new
#Tezos
node that will be written in the
@rustlang
! Check out our blog post for more information.
Now on
@TezosAgora
(link below):
An explanation and prototype from the Marigold/
@LigoLang
teams about adding views to Tezos, boosting composability.
They intend to propose it in the amendment proposal process after Babylon (scheduled to activate in mid-October).
Prototype adding views to Tezos. It should make interactions between smart-contracts much easier!
We hope to include this in the next amendment proposal process.
@LabosNomades
will also release important shell upgrades in the coming weeks, which will include the transition to the Irmin2 backend from
@tarides_
as well as some easily deployable smart contracts (e.g. multisig, assets)
Update on Babylon from
@LabosNomades
based on feedback
The tweaked proposal would make transition easier for bakers and developers using custom signers
Babylon update: after receiving some feedback on the Babylon proposal, we'd like to propose a tweaked version on Friday, since there is still some time.
Significant improvements to Michelson which make it easier to write and make it a much better compilation target for high-level languages led by
@SmartPy_io
,
@LigoLang
, and
@serokell
)
Tooling
- Nearing release of an indexer, an improvement on the earlier Mezos indexer to be used for Cortez
- Compilation of the Tezos code base to JS, enabling Tezos in the browser
- Try-Michelson: a web interface/editor for playing with Tezos smart contracts w/o their own node
If accepted by the
#tezos
community, the Babylon upgrade would activate in mid-October this year
For detailed documentation to assist wallets and application developers in the transition to Babylon, follow along here:
This is a critical read about the upgrade to Babylon (i.e. PsBABY5Q...) for anyone who implements delegation in a Tezos wallet
A link has been added under key resources for Babylon here:
Post ๐ฆ BABY5 ๐ฆ (Babylon) injection, what next? More docs and
@reddit
AMA soon! Remember that there is a thread of all publications (us and
@LabosNomades
), changelog included, explaining all the features that this
@tezos
proposal includes. Stay informed:
Or check out this TL;DR
Beyond all the improvements (e.g. Emmy+, improvements to Michelson, hardened governance mechanisms, etc.), this is the first Tezos proposal injected on behalf of multiple teams (
@LabosNomades
,
@CryptiumLabs
, and
@LigoLang
)
account overhaul to distinguish accounts (tz1, tz2 and tz3) and smart contracts (KT1)
- Makes implicit accounts (i.e. tz1, tz2, and tz3 accounts) able to delegate and KT1s are for contracts
- Replaces KT1 accounts with formally verified KT1 script (with same semantic)
Protocol: Michelson
- Extending functionality to allow multiple entrypoints and remove most restrictions of big_map's
- Improved gas cost model, based on new benchmarks
N.b: multiple EPs will be implemented so as to ensure reverse-compatibility for prior contracts
Protocol: Miscellaneous
- Account re-haul: enabling implicit accounts to be delegatable and removing script-less KT1s
- Harden the upgrade mechanism through quorum cap/floor and a modest proposal quorum (5% in recent blog post)
Shell
- Shell upgrade this summer will include a significantly improved storage back-end
- A mempool that is further hardened against spam attacks
- A modestly refined p2p layer to improve connectivity, network topology, and peer discovery
๐This week,
@AnnaRRose
catches up with
@JacobArluck
, Marco Stronati and Marc Beunardeau from
@LabosNomades
to chat about
@tezos
, the community, governance, and how they are incorporating zk proofs - and specifically
#Zcash
's Sapling - into their system.
A new 5% proposal quorum and quorum floors/caps
- A Proposal requires 5% support in the Proposal Period to proceed to the Exploration Vote Period
- Quorum floor of 20%, quorum cap of 70%
Motivations discussed in these:
Tezos address tz1Kt4P8BCaP93AEV4eA7gmpRryWt5hznjCP voted "yay" with 164 rolls on
#Tezos
proposal "Babylon 5"
Vote status is 100.00% yay/0.00% nay, with 0.39% remaining to reach 72.91% quorum for the exploration phase.
"On-chain governance permits the emergence of strong cultural norms around the process of protocol change."
Speaking of which.. this post has been added to the new "Philosophy and Economics" section of
@TezosAgora
:
@Shaughnessy119
2 overlooked elements of
#tezos
upgrade process:
1. Must reach high level of consensus (e.g. 80% supermajority of quorum) *repeatedly* over 3 months to upgrade
2. Required consensus only changes *gradually* (via quorum adjustment), not massively at once
It advances
@tezos
from simply upgrading constants (i.e. Athens) to constant upgrades
The consensus algorithm, smart contract functionality, and the governance mechanism itself are all being upgraded
Broke it down here:
That said, it hasn't been a simple, straightforward road.
Babylon 2.0.1 has been one of the greatest tests of the
@tezos
amendment process and the community's social consensus to date:
@VitalikButerin
Also, ICYMI ...
@TezTechLabs
gave an update on Velos yesterday:
"we have developed Velos to the point where we are able to open source our 2nd level protocol in September. [..] we are looking to launch a Velos Node through an existing baking service."
for those who might cite
@VitalikButerin
's post re: L1 gov overhead, he notes:
"It's important to note that if there is any problem with the base layer implementation, it's possible to simply use the smart contracts while being fixed or even deleted."
Conscious efforts to ensure downstream stakeholders are aware, try it out on testnet, and start adjusting early mitigates upgrade risk.
This is one of the leading motivations behind
@TezosAgora
, as outlined in last week's post:
Mentions current work by
@cryptoeconlab
to implement
@plasma_group
's OVM on
@tezos
using
@LigoLang
!
"biggest benefit of the OVM is we will soon be able to use many other L2 constructions such as State Channels and Optimistic Rollups as soon as their implementation is released."
@Blindripper85
@TQTezos
It's a simple, but fully-fledged DAO framework for
@tezos
Was hoping to share a preview this month, but looking more like January
If youโre deciding whether to trust a companyโs privacy promises, the motivations of individual employees are irrelevant. Instead, what matters is whether those promises align with the companyโs business model.
@js_horne
Massive here strikes me more as internet scale (i.e. all humanity but bounded by transaction costs like language), rather than real-world institutions like cities
Managing a *massive* global, high-stakes online tournament seems like a good early one
@spencernoon
growing composability, which presents a collective action problem for projects considering a new platform
a project doesn't want to leave unless its composable complement go with it (distinct from simple network effect)