R2

[R2 @Unh00ked]

@Usernamecrypto2 ser since when do you trade like me :D

[R2 @Unh00ked]

@Shawred0 This aged well

[R2 @Unh00ked]

@gem_insider Still here

[R2 @Unh00ked]

Verifying my Twitter account for my #GalxeID gid:5BerBTyEK7ptYyBG8YjeL4 @Galxe

https://t.co/KUunSE053x

[MEXC @MEXC]

.@MazzeLabs, a Layer 1 blockchain that redefines performance through its PoW-based DAG architecture, achieving 40,000 TPS and 1s finality, is coming to #MEXCKickstarter 🚀

🗳Vote with $MX to share massive airdrops
📈 $MAZZE/USDT Trading: 2024-05-17 14:00 (UTC)

Details: https://t.co/3zGqbbTl7T

[R2 @Unh00ked]

@theionicXBT $MAZZE, L1 DAG, POW, ZK, 40K tps, targeting 100K, less than 20MC

[R2 @Unh00ked]

@FiskerInc Hello to raise cash, have you thought about going the DeFi route and releasing shares of the company via a crypto token? Ofc clear it with the SEC and prolly seek council from #coinbase

[Crypto Research (Daily Share) @Brc20N]

#Mazze and Kaspa are both innovative blockchain platforms utilizing DAG architectures, yet they differ significantly in their approach to implementing smart contract functionalities.

We have successfully integrated smart contract capabilities by adapting the EVM to work with our DAG structure. This adaptation involved implementing two key solutions: the Weighted Ledger Selection Rule (WLSR) and the DAG-Embedded Tree Structure (DETS) (more about WLSR and DETS in Consensus Mechanism in WP). These modifications ensure that the EVM can operate efficiently within a non-linear blockchain structure, facilitating reliable smart contract execution even in a DAG environment.

On the other hand, Kaspa started with a different structural approach and has not yet integrated smart contract capabilities. Their initial design does not natively support the traditional EVM, and thus they would likely need to develop a unique virtual machine tailored to their DAG architecture to handle smart contracts.

Our platform leverages an adapted version of EVM, which means we didn’t have to develop a completely new system from scratch. Instead, we focused on adapting and optimizing an existing, proven technology to fit our unique needs. This approach has allowed us to deploy smart contracts more quickly and efficiently.

Kaspa has chosen to build their blockchain technology from the ground up without using pre-existing frameworks like Substrate or Cosmos. This ambitious approach allows for significant customization and optimization specific to their goals but also means a longer development time for complex features like smart contracts.

Both platforms have different strategic focuses and roadmaps. Mazze has prioritized the integration of smart contracts early in its development, recognizing the demand and utility these features bring to users and developers. In contrast, Kaspa might have prioritized other aspects of blockchain technology, such as scalability and speed, before tackling the complexities of smart contract integration.

[R2 @Unh00ked]

@gem_insider Which L2?

[R2 @Unh00ked]

@CrptoProfess0r $MAZZE for me. 1B mcap easily achievable. L1 with privacy and EVM

[R2 @Unh00ked]

@xgremlin Check out $mazze, DAG based L1 like KASPA but with privacy. Test net launching soon

[R2 @Unh00ked]

@Shady_ocs_16 Dam missed it.

[R2 @Unh00ked]

Yay @mazzelabs

$Mazze

[R2 @Unh00ked]

@theionicXBT Look at $mazze, L1 with privacy built in, less than 10MC

[R2 @Unh00ked]

@screentimes 6zBcqssY2ip7LAhLNRN5V9cnNsWSkeHDL8usah7tiamb

[R2 @Unh00ked]

@0xBunzy @KeroNFTs @Zach_XPT BOOOLISH

[R2 @Unh00ked]

@KeroNFTs fuck it I am in.

[R2 @Unh00ked]

@MarketCapOf https://t.co/XddfApsyKA

[R2 @Unh00ked]

@ChadCaff possibly moving to $Sol

[R2 @Unh00ked]

@leviathancrypto Are you posting this on your discord?