Yokay Gnoma 💢 ⛺ 🧙‍♂️,🧙‍♂️ Morph Tabi

almost 3 years ago

Just joined Epoch 3 of $tip from @tipcoineth! You can view the chart here: https://t.co/3fY6CeeRdk

143

9 months ago

Traditional blockchains struggle with real-time prediction markets — too slow, too crowded. Linera’s microchains change that: every user gets their own parallel chain, enabling instant, scalable transactions. This is how prediction markets become truly live. @linera_io

Oxy π² 🍊,💊 HUDL StratoVM 🧙‍♂️/acc (✧ᴗ✧)

10 months ago

🚀 Excited to see the partnership between @acurast & @linera_io! Thousands of blockchains will run as Linera microchains on Acurast’s edge fleet — unlocking massive scalability, performance, and decentralization for Web3. Future of blockchain starts here 🔥 #Acurast #Linera #Web3

Yokay815 retweeted

LiLLy @LIQDLilly

10 months ago

Introducing: LiLLy Alpha Your hyperEVM alpha source: top projects, streamer tokens, LP strategies, and airdrop farming. Exclusive access: Hodl 10M $LiLLy tokens. Join the waitlist on https://t.co/lwZBTI0Oln P.S. there will be goth baddies

63K

Who to follow

Asrulialasri.ink

@AsruliaL

@Oxyyy96

@nexchain_ai Nitrograph

Shanaa

@Zenosamha

10 months ago

@linera_io gmicrochains

11 months ago

We’re entering a new Internet era—millions of AI agents running transactions every hour. 🚧 Major L1s aren’t built for this. 🤝 Cross-chain composability is lacking. 👤 Infra is still human-centric. ✅ Solution: Linera — blockchain for the real-time, agentic Web. @linera_io

11 months ago

@YourT1me 0xc7b79aAd0F2B68D8B8672Ea81D9d671D0A7a0cB4

11 months ago

@PlayFarlegacy https://t.co/IkFH8LDYV6

Yokay815 retweeted

11 months ago

🚀 Dubhe Engine Execution Model Logic and Data Decoupling Execution Flow ⚙️ In Dubhe Engine, business logic execution is completed by system modules, while state reads and writes are performed through Schema modules. 🔀 This decoupling allows developers to independently evolve logic and data structures: 🧱 When Schema structures need expansion or modification, old data can be migrated to new Schema through migration scripts (such as migrate.move) and hot upgrade mechanisms provided by Dubhe. Business logic changes can also be implemented by publishing new system module versions without affecting underlying storage layouts. During execution, system modules cooperate closely with Schema modules. 📦 For example, when system logic needs to create a new object instance, it actually calls Schema modules to create that object in on-chain resource storage and assign a unique key. 🔍 When system logic queries or modifies attributes, it also accesses or updates corresponding fields through functions provided by Schema. 🧩 This pattern can be compared to Entity-Component-System (ECS): -Schema defines components (data) -System modules play systems (logic) -Certain on-chain object IDs are similar to entities, Mounting different components to entities through dynamic fields. 🚀 The result is higher modularity and upgradeability of on-chain state models while ensuring performance, similar to upgrading from manual low-level storage management to using high-level database ORM development experience. #DubheEngine #Move #Sui #Web3infra #SmartContracts #Web3 #BlockchainDev

DubheEngine's tweet photo. 🚀 Dubhe Engine Execution Model

Logic and Data Decoupling Execution Flow

⚙️ In Dubhe Engine, business logic execution is completed by system modules, while state reads and writes are performed through Schema modules.

🔀 This decoupling allows developers to independently evolve logic and data structures:

🧱 When Schema structures need expansion or modification, old data can be migrated to new Schema through migration scripts (such as migrate.move) and hot upgrade mechanisms provided by Dubhe.

Business logic changes can also be implemented by publishing new system module versions without affecting underlying storage layouts.

During execution, system modules cooperate closely with Schema modules.

📦 For example, when system logic needs to create a new object instance, it actually calls Schema modules to create that object in on-chain resource storage and assign a unique key.

🔍 When system logic queries or modifies attributes, it also accesses or updates corresponding fields through functions provided by Schema.

🧩 This pattern can be compared to Entity-Component-System (ECS):

-Schema defines components (data)

-System modules play systems (logic)

-Certain on-chain object IDs are similar to entities, Mounting different components to entities through dynamic fields.

🚀 The result is higher modularity and upgradeability of on-chain state models while ensuring performance, similar to upgrading from manual low-level storage management to using high-level database ORM development experience.

#DubheEngine #Move #Sui #Web3infra #SmartContracts #Web3 #BlockchainDev

19K

Yokay815 retweeted

11 months ago

🚀 Dubhe Engine Execution Model Events and Transaction Processing 🧾 Dubhe-generated Schema modules also automatically generate corresponding event types for each data structure. ⚡ System modules can trigger these events during transaction execution to record important state changes. 📦 These events are recorded in block logs by the underlying chain. 🔍 On one hand, events improve transparency of on-chain state transitions, enabling offline analysis or indexing tools to capture key changes.On the other hand, components like Dubhe Indexer subscribe to on-chain event streams, implementing event-driven state synchronization. ⛓ Therefore, whenever transaction processing is completed (confirmed through consensus), associated state modifications and events can be quickly reflected in off-chain data views through Indexer.🖥 This provides near real-time state updates for frontends and developers. 🧠 In summary, Dubhe Engine's execution model innovates on-chain state management through Schema/System layering and dynamic fields, while following underlying chain Move VM transaction processing flows. 🔧 This brings: Clearer contract structures 🏗 More convenient state expansion 📈 Stronger support for complex on-chain applications like game worlds 🎮 ✅ Developers no longer need to worry about tedious low-level storage layouts and can focus on writing high-level business logic. Dubhe has already built robust infrastructure for state transitions and data management at the engine layer. #DubheEngine #Move #Sui #Web3infra #SmartContracts #Web3 #BlockchainDev

16K

Yokay815 retweeted

11 months ago

On-chain security OR real-time performance? Why not both?🤔 See how we do it 👇 1/Dubhe Engine itself is not an independent blockchain, so it does not introduce new consensus algorithms. Applications built with it ultimately deploy and run on existing infrastructure chains, such as Sui, etc. ⚡ This means transaction confirmation and on-chain state reliability of Dubhe DApps completely rely on the consensus mechanisms and security of corresponding underlying chains. Taking Sui as an example 🟢, it uses Narwhal/Bullshark consensus 🦈 (a high-performance Byzantine fault-tolerant protocol) to order and confirm transactions; Dubhe applications on Sui also go through this consensus process to reach final state. ✅ Once transactions are confirmed by underlying chain consensus, Dubhe's on-chain module execution results are considered immutable on-chain facts. For developers 👨‍💻, there's no need to concern themselves with consensus implementation details to trust that Dubhe application states have the same security and consistency as other applications on the underlying chain. 2/Because application states are stored on underlying blockchains, Dubhe inherits underlying chain data availability guarantees — all blocks and state data submitted on-chain are propagated in the chain's peer-to-peer network 🌐 and stored by full nodes 🖥️, ensuring anyone can access and verify this data in the future. Based on this, Dubhe further enhances data accessibility for developers through built-in indexers 📊. Dubhe Indexer directly connects to blockchain nodes or full node RPC interfaces, monitors new blocks and events ⏱️, extracts and stores Dubhe application-related data in developer-owned databases. This off-chain replica 🗄️ ensures applications don't need to rely on on-chain nodes when reading historical states or complex queries, improving query efficiency ⚡ and reliability. When blockchains experience temporary network partitions or node desynchronization ⚠️, local data replicas maintained by Dubhe Indexer can also provide cache support to some extent, ensuring smooth operation of application frontends. 3/Worth mentioning 📝, Dubhe Indexer adopts a real-time, event-driven architecture ⏩ that can immediately push changes when on-chain data updates. This is crucial for building real-time interactive on-chain games 🎮 or applications 📱: after users trigger transactions in DApps, not only do they get confirmation through underlying chain consensus ✅, but Indexer immediately provides new states to the application layer, achieving real-time synchronization of frontend interface states 🔄. Therefore, from the perspective of application developers and users 👩‍💻👨‍💻, Dubhe not only utilizes underlying chain consensus to guarantee data reliability 🔒 and availability 📡, but also makes data usable through its own indexing mechanism, making it always available for efficient querying and response ⚡. This is also one of Dubhe Engine's important characteristics 🌟 for real-time on-chain applications. #DubheEngine #Move #Sui #SmartContracts #Web3 #BlockchainDev

DubheEngine's tweet photo. On-chain security OR real-time performance?

Why not both?🤔

See how we do it 👇

1/Dubhe Engine itself is not an independent blockchain, so it does not introduce new consensus algorithms.

Applications built with it ultimately deploy and run on existing infrastructure chains, such as Sui, etc. ⚡ This means transaction confirmation and on-chain state reliability of Dubhe DApps completely rely on the consensus mechanisms and security of corresponding underlying chains.

Taking Sui as an example 🟢, it uses Narwhal/Bullshark consensus 🦈 (a high-performance Byzantine fault-tolerant protocol) to order and confirm transactions;

Dubhe applications on Sui also go through this consensus process to reach final state.

✅ Once transactions are confirmed by underlying chain consensus, Dubhe's on-chain module execution results are considered immutable on-chain facts.

For developers 👨‍💻, there's no need to concern themselves with consensus implementation details to trust that Dubhe application states have the same security and consistency as other applications on the underlying chain.

2/Because application states are stored on underlying blockchains, Dubhe inherits underlying chain data availability guarantees — all blocks and state data submitted on-chain are propagated in the chain's peer-to-peer network 🌐 and stored by full nodes 🖥️, ensuring anyone can access and verify this data in the future.

Based on this, Dubhe further enhances data accessibility for developers through built-in indexers 📊.

Dubhe Indexer directly connects to blockchain nodes or full node RPC interfaces, monitors new blocks and events ⏱️, extracts and stores Dubhe application-related data in developer-owned databases.

This off-chain replica 🗄️ ensures applications don't need to rely on on-chain nodes when reading historical states or complex queries, improving query efficiency ⚡ and reliability.

When blockchains experience temporary network partitions or node desynchronization ⚠️, local data replicas maintained by Dubhe Indexer can also provide cache support to some extent, ensuring smooth operation of application frontends.

3/Worth mentioning 📝, Dubhe Indexer adopts a real-time, event-driven architecture ⏩ that can immediately push changes when on-chain data updates.

This is crucial for building real-time interactive on-chain games 🎮 or applications 📱: after users trigger transactions in DApps, not only do they get confirmation through underlying chain consensus ✅, but Indexer immediately provides new states to the application layer, achieving real-time synchronization of frontend interface states 🔄.

Therefore, from the perspective of application developers and users 👩‍💻👨‍💻, Dubhe not only utilizes underlying chain consensus to guarantee data reliability 🔒 and availability 📡, but also makes data usable through its own indexing mechanism, making it always available for efficient querying and response ⚡.

This is also one of Dubhe Engine's important characteristics 🌟 for real-time on-chain applications.

#DubheEngine #Move #Sui #SmartContracts #Web3 #BlockchainDev

21K

Yokay815 retweeted

11 months ago

🎉 Win $STARS – Lucky Draw #4 We're excited to launch Dubhe's final lucky draw — a fun giveaway for our amazing community! Next month, we'll be launching a brand-new campaign for the community. ❤️How to enter:https://t.co/7s49RcRINV ⏰ Ends: Sep 1, 12 PM UTC ✅Connect your Sui wallet address to Galxe ✅Complete the Galxe tasks 🎁 Rewards: 🏆 400 winners will be randomly selected 🤩 Each will receive 100K $STARS Join now for your chance to win. 💫

32K

@Tabichain #TABI #Tabizen

11 months ago

11 months ago

@Tabichain #TABI #Tabizen LFG

11 months ago

@morphnetwork let him cook Morph

11 months ago

@morphnetwork 🚀 Excited to explore Morph, the next-gen Layer 2 bringing seamless scalability & user-friendly dApps! Can’t wait to see how it shapes the future of Web3. 🔥 #Morph #Layer2 #Web3 @morphnetwork

Yokay815 retweeted

12 months ago

🚀 Dubhe Engine Execution Model Move VM & Transaction Execution Dubhe Engine's model is based on Move smart contract paradigms & chain transaction processing, but adds a unique Schema-System separation 🧩 to optimize state & logic execution. 🔄 When user txns (e.g. DApp ops) hit the blockchain ⛓️, consensus triggers Move VM to run contract functions. 📦 For Dubhe apps, these txns mainly call system module functions (built by Dubhe/devs). 📖 Move VM reads Schema-stored data 📚 per on-chain state, applies business logic ⚙️, changes state, triggers events, then atomically commits changes. 🔐 All follows Move security: no illegal resource copies/loss, txns fully succeed or rollback, ensuring correct & atomic state transitions. #Move #DubheEngine #BlockchainDev #Web3 #Sui

DubheEngine's tweet photo. 🚀 Dubhe Engine Execution Model

Move VM & Transaction Execution

Dubhe Engine's model is based on Move smart contract paradigms & chain transaction processing, but adds a unique Schema-System separation 🧩 to optimize state & logic execution.

🔄 When user txns (e.g. DApp ops) hit the blockchain ⛓️, consensus triggers Move VM to run contract functions.

📦 For Dubhe apps, these txns mainly call system module functions (built by Dubhe/devs).

📖 Move VM reads Schema-stored data 📚 per on-chain state, applies business logic ⚙️, changes state, triggers events, then atomically commits changes.

🔐 All follows Move security: no illegal resource copies/loss, txns fully succeed or rollback, ensuring correct & atomic state transitions.

#Move #DubheEngine #BlockchainDev #Web3 #Sui

21K

Yokay815 retweeted

12 months ago

🚀 Dubhe Engine Execution Model Data Schema and State Transitions Dubhe introduces Schema as state storage units, dramatically changing traditional Move contract state management methods. 🧱 Developers define data structures (Schema) in declarative syntax in project configuration, including fields, events, and error types. ⚙️ By running the schema:gen command, Dubhe CLI reads these definitions and automatically generates corresponding Move modules, implementing these Schema storage logic on-chain. 🔧 Generated Schema modules utilize Move's dynamic fields mechanism at the bottom layer, allowing contracts to flexibly add or modify storage fields without changing existing storage structures. 🗃️ This mechanism is similar to maintaining an extensible key-value store on-chain, decomposing complex data objects into manageable units at the bottom layer. 🔁 Therefore, when a transaction triggers state transitions, system module logic calls APIs provided by Schema modules to complete on-chain data reads and writes, ensuring data structure consistency and integrity. #DubheEngine #Move #Sui #Web3infra #SmartContracts #Web3 #BlockchainDev

DubheEngine's tweet photo. 🚀 Dubhe Engine Execution Model

Data Schema and State Transitions

Dubhe introduces Schema as state storage units, dramatically changing traditional Move contract state management methods.

🧱 Developers define data structures (Schema) in declarative syntax in project configuration, including fields, events, and error types.

⚙️ By running the schema:gen command, Dubhe CLI reads these definitions and automatically generates corresponding Move modules, implementing these Schema storage logic on-chain.

🔧 Generated Schema modules utilize Move's dynamic fields mechanism at the bottom layer, allowing contracts to flexibly add or modify storage fields without changing existing storage structures.

🗃️ This mechanism is similar to maintaining an extensible key-value store on-chain, decomposing complex data objects into manageable units at the bottom layer.

🔁 Therefore, when a transaction triggers state transitions, system module logic calls APIs provided by Schema modules to complete on-chain data reads and writes, ensuring data structure consistency and integrity.

#DubheEngine #Move #Sui #Web3infra #SmartContracts #Web3 #BlockchainDev

17K

Yokay815 retweeted

12 months ago

🚀 Join the Dubhe X Community! 👉https://t.co/teHTnOrjHK We've just launched our official X Community —a dedicated space for Dubhe builders and content creators to connect, collaborate, and grow together. Whether you're a developer, gamer, or Web3 explorer, you're welcome here. Let's build the future of on-chain applications together 💫

DubheEngine's tweet photo. 🚀 Join the Dubhe X Community!

👉https://t.co/teHTnOrjHK

We've just launched our official X Community —a dedicated space for Dubhe builders and content creators to connect, collaborate, and grow together.

Whether you're a developer, gamer, or Web3 explorer, you're welcome here.

Let's build the future of on-chain applications together 💫

20K

Yokay815 retweeted

11 months ago

🎉 Win $STARS – Lucky Draw #3 🍀 We're thrilled to kick off Dubhe's third lucky draw — a fun giveaway for our amazing community! ⏰ Ends: August 18, 12:00 PM UTC ❤️ How to enter:https://t.co/N5gZQS8ON1 ✅ Connect your Sui wallet address to Galxe ✅ Complete the Galxe tasks 🎁 Rewards: 🏆 300 winners will be randomly selected 🤩 Each will receive 100K $STARS Join now for your chance to win. 💫

106

29K