Implementing the JAM Graypaper to bring forth the next iteration of Polkadot ✨ Maintaining https://teapawt.net/t.co/jrlDke1tM0 and https://teapawt.net/t.co/EAUwZVeuHp
Worldwide
Joined November 2024
- Tweets37
- Following16
- Followers322
- Likes50
A small video of how a 6 node local network looks like, displayed in a 3x2 grid.
The green node is the block author and the gray ones are the receivers.
You can see blocks being received pretty much immediately (it runs locally). It also uses 1 instead of 6 second block times to make it more interesting.
The authors of the first epoch (12 blocks) are fixed to round-robin. Afterwards it switches to a ZK-VRF to anonymize who will author the next blocks, it is random.
JamBrains retweeted
JAM continues progressing from research to real implementation.
Independent JAM implementations are now being x-rayed through automated conformance fuzzing systems designed to scrutinize state transition function against the canonical JAM Gray Paper specifications.
The objective is to surface discrepancies between implementations, identify edge cases, and verify that independent clients faithfully follow the protocol standards defined in the Gray Paper.
We now passed all 5 steps of the M1 conformance testing 🥳
This will be noted in a Smart Contract on Paseo Hub as a stamp of approval. Looks like only TurboJam was faster than us to pass all tests 🥈
12 hours of fuzzing. ~740k blocks tested.
Most of the errors in the logs are intentional. The fuzzer is checking whether the client correctly rejects invalid blocks.
Stage 2 of 5 for @jam_brains, the voluntary JAM implementer team at Parity, working through the hard parts in public.
👏 @bkchr
JamBrains retweeted
New URL for my bookmarks -> jamtoaster.network/
The supercomputer hidden in an underground bunker in Portugal, simulating the next gen JAM blockchain
JAM Implementer Teams - the automated fuzzer to test JAM implementations is now accessible here: fuzz.jamtoaster.network/
Please note that you will need to register and be approved, and need ~ 0.5 DOT to use it. Also please note that this is only for JAM implementer teams.
If all is successful, you can attest on-chain and then set up an interview with the Polkadot Technical Fellowship.
See the "Let's JAM" channel on Matrix ( #jam:polkadot.io ) for more details.
Fuzzing our client since 12 hours now for about 740k blocks 💪
There are many errors in the logs, which indicates that the fuzzer is testing whether our client is correctly rejecting invalid blocks.
But this is just the second of five stages, and we need to pass all of them 🤞
JAM continues to progress from research to real-world implementation.
Independent JAM implementations are getting x-rayed with an automated JAM fuzzer verification system. The goal is to surface discrepancies between a team's implementation and the canonical Gray Paper specs.
JAM (Join Accumulate Machine) is Polkadot’s next-generation decentralized compute protocol designed for scalable and trust-minimized execution.
We announce the prototype of our JAM Service playground: playground.jamcha.in/
It allows you to write JAM Services in C23 and execute them immediately. Check out the examples that use our own service SDK.
Now that C works, Python is next 🐍
JAM development is advancing rapidly this week and it is getting more competitive.
Most teams are on version 0.7.0 of the Gray Paper. It is also the first time that we got performance metrics - even nicely rendered.
We are not on the list yet, but remain thrilled to where we will land 👇
First look at overall performance across JAM Implementors. Polkajam leads; JamZig (pure Zig language) is already competitive with debug logs enabled. Stripped benches coming soon — and yes, we expect to push this up! ⚡🤠
@Polkadot @ziglang #JAMProtocol
Already tinkering with it. Left side GrayMatter and right side JamZig 🤝
Block hash ✅
Initial state root ✅
Posterior state root⏳
(Hint: this is very good for @Polkadot JAM)
A productive weekend it seems, just released the:
JamZig⚡ M1 v0.6.6 Fuzz Target 🤠
github.com/jamzig/conformanc…
Happy Fuzzing!
#JAMProtocol @polkadot @polkaworld_org
Oh hey that's us
As @OliverTaleYazdi explains here, he is one of 4 Parity folk (with @cisco_aguirrep @kianenigma & Maciej Z) working on a non-Parity JAM implementation.
They're called @jam_brains
JamBrains retweeted
🧠 Meet the teams implementing the JAM Protocol.
Filmed at Sub0 Reset in Bangkok, this interview series explores how several implementer teams envision JAM, Web3, and the future of decentralized computing.
The first episode drops this Thursday.
Watch the teaser 👇
JamBrains retweeted
Come watch the builders themselves talking about JAM!
Two members representing @jam_brains along with @tomusdrw from @fluffylabs_dev and @danicuki from @jamixir
This quoted post is unavailable.
We just published our new API endpoint to validate JAM test vectors 🎉
This allows other teams to test their block authoring logic without the need to share binaries. The format is the one that @colorfulnotion introduced for this purpose.
We will extend this to work for more presets and formats; currently it only supports "tiny" and JSON. Eventually, we want to have most of our State-Transition-Function (STF) accessible through an API. Stay tuned 🤘😎
dev.jamcha.in/#/Functions/Gm…
JamBrains retweeted
JAM call happening now! 26+ @polkadot JAM implementors from 13 teams developing in different programming languages: Elixir, Go, Python, Rust, C++, Zig, TypeScript, Scala.
When @gavofyork drops rumours on future @Polkadot JAM improvements:
- Quantum Resistance
- JAM Grid (interoperable JAM chains)
- CoreVM
- Service SDK
Count us in for building this!
You’re unable to view this Post because this account owner limits who can view their Posts. Learn more