⛏️ MT 🤖

@spoonforhoney As long as I can zoom from @hoffmang yacht ⛵

@digdotnet Zoom beer party??

Well it would be nice to get the builders together more frequently to have a more unified effort to push things forward. I honestly feel by myself and alone sometimes and could use the motivation of having some beers with like minded folks.

@digdotnet sign me up

I think I might be ready for a very limited alpha #DIGNetwork testnet soon

Bacon in the morning!

getting good at those custom action layer🧩's

@DracattusDev Me to!

I must have one!!!

@Rigidity16 @Tangem @DrLeoSpacemn @yakuhito There isn't much novel going on, And @Tangem has clearly left an unfulfilled infrastructure need by getting too greedy. You could build an open protocol, and you would actually be fulfilling the original vision, you know the one we all bought into.

@digdotnet @Tangem @DrLeoSpacemn @yakuhito I would be lying if I said the thought hasn't crossed my mind...

used to open a CEX just to swap tokens like it was 2019. now i just... do it from my Tangem. feels illegal how easy that is 🃏

@Rigidity16 @Tangem @DrLeoSpacemn @yakuhito Maybe you should build a "Sage Card" and become a competitor since @Tangem isn't interested in ecosystem partners. I'm pretty sure you could do it. And I'm also pretty sure you could do it better.

@Rigidity16 @Tangem @DrLeoSpacemn @yakuhito I do think they shot themselves in the foot here by eliminating vectors of adoption. Restricting integrations is not how you scale. They have demoted themselves from must-have infrastructure to niche product with limited life span. But I'm sure they think they know better 🤣

@Rigidity16 @Tangem @DrLeoSpacemn @yakuhito @Rigidity16 to be fair to @Tangem they did fix it the last time we all complained, updated 3 months ago: github.com/tangem/tangem-… before it specifically said that copying in any form was disallowed, now they have a carve out for personal use.

@Tangem @DrLeoSpacemn @yakuhito Your license is contradictory. Fix it.

Pew Pew!

@M_Kirk @abrahamsewill Yea, now that you spell it out, I suppose you could.

@digdotnet @abrahamsewill What I'm hearing is I can farm on L1, then stake my rewards into a L2 validator (and once we grow a fee market: perhaps earn fees from _both_ levels)? LFG!

The L2 I'm working on is a from-scratch implementation in Rust, designed to be a 1:1 match with Chia's Coinset model and CLVM. In theory, existing Chia puzzles should work natively on it, though I'm still proving that out. Instead of plotting, validators lock XCH collateral on the Chia L1. Block progression is gated by finality checkpoints: soft finality must be reached between epochs, and hard finality (an L1 snapshot) must be reached at the end of each epoch. This design allows L2 blocks to be produced significantly faster than L1 blocks while still inheriting L1 security guarantees. The goal is faster decentralized state progression for application data, while keeping financial assets settled on the L1. Together with the L1, this creates a full synergistic stack for next-generation blockchain applications.

@abrahamsewill Yea, but that proof in itself is secured by the L1 PoST

@digdotnet A proof of stake L2?

It was much less complex than I expected achieving finality on the L2 for the simple fact that leveraging the L1 for validator registration you have a known validator set.

Some more WIP snapshots

#Chia L2 milstone, first $DIG transfer on the L2