MarvelCrypt | 3D Motion Designer (❖,❖)

3.7K posts

MarvelCrypt | 3D Motion Designer (❖,❖) banner
MarvelCrypt | 3D Motion Designer (❖,❖)

MarvelCrypt | 3D Motion Designer (❖,❖)

@marvelcryptic

3D Animator | Video Creator | Blender & Premier Pro | Designer @ritualnet Ambassador @poddotnetwork

Katılım Mayıs 2024
1.3K Takip Edilen1K Takipçiler
Priscilla (❖,❖)
Priscilla (❖,❖)@usochukwuu·
Most NFT projects try to create their identity after launch but @zelijOrigins starts with one already, It is an identity based on centuries-old Moroccan tradition, this makes it more interesting for me. The collection is rooted in Zelij, a traditional Moroccan mosaic craft. This is a centuries-old art built on symmetry, geometry, repetition and human precision. It’s not just a collection “inspired by” Moroccan culture; the craft itself underpins every design. Only 888 unique pieces of this art will exist on ethereum Each NFT will be 1/1 The artist @ismailiwi1 is a Moroccan creative known for physical mixed-media works pointillist portraits made of salt, hammered nail art, concrete sculptures, even architectural shadow pieces. This renders a good credibility most digital-only NFT collections lack. His work has been recognised by major institutions like Real Madrid and PSG, proving he’s not an anonymous “overnight” web3 artist. The story and process behind each piece make it feel more meaningful than a collection driven by hype. Yeah, I am so bullish on this project.
Priscilla (❖,❖) tweet media
Priscilla (❖,❖)@usochukwuu

How to get @ZelijOrigins pls?

English
2
1
9
181
Siggy
Siggy@Siggyworld·
male peak performance:   - girlfriend/wife > 1 btc - 6 pack - minimum 1 x bench/1.5x squat - 10+ pull ups, 30” vertical min - has read meditations   - averages 7+ hours of sleep - walks 10k steps a day - 24 hour fasts - eats well, 1 gallon of water - loves ritual - siggy testnet mint access code
Siggy tweet media
English
8
4
34
550
El-Khalīl
El-Khalīl@El__khalil·
just say “lol” and move on
English
4
0
11
91
Blokyz
Blokyz@OriginalBlokyz·
All our Archetypes belong one of 5 classes - Mystery, Commons, Seekers, Makers and Relational. The relational ones are usually aftereffect when a common encounters a seeker or a maker. For reference this one is when a Knight encounters a Dark mage and gets converter into a Dark Knight.
Blokyz tweet media
English
193
76
410
18.2K
Meison (❖,❖)
Meison (❖,❖)@meison_mswen·
Ritual Testnet Stats: Week 5 Let’s look at Ritual through the numbers again. This time, the context matters. Week 1 looked like the HTTP week. The main question was simple: can contracts reach outside the chain? HTTP was the obvious primitive to test first because it is easy to understand, easy to call, and easy to build around. Week 2 became more agent-shaped. Sovereign Agent started moving up, and the signal changed. Builders were not only asking for data anymore. They were starting to test agents as execution primitives. Week 3 looked more balanced. HTTP, Long-Running HTTP, Sovereign Agent, DKMS, LLM, and media calls started to look like parts of one stack. That was the first week where Ritual activity felt less like one feature winning and more like builders climbing the stack. Week 4 made the async layer harder to ignore. Sovereign Agent led again, but the bigger story was transaction flow: async commitments, async settlements, and scheduled execution started taking most of the window. So Week 4 was not just agents are active. It was: agents are active inside async workflows. Now Week 5 matters because the pattern did not disappear. It repeated. EIP-1559 is still the biggest single transaction category at 32.93%. That is normal. Builders still need regular EVM activity. They deploy contracts, call functions, test interfaces, and move through the usual development loop. But regular EVM activity is only about one third of this window. The other two thirds are scheduled and async transactions. Scheduled is 15.37%. Async Commitment is 20.16%. Async Settlement is 31.54%. That changes how I read the network. This does not look like a testnet where people only send simple calls and click buttons. It looks like work is already moving through phases. A scheduled transaction means something is meant to happen later. An async commitment means work entered an execution flow. An async settlement means a result came back and had to be settled. So the basic unit is no longer only transaction. It starts to look like workflow. The precompile stats make that clearer. Sovereign Agent leads again at 31.4%. HTTP Call follows at 27.5%. Long-Running HTTP is third at 15.7%. That is almost the same shape that started becoming visible in Week 4. Agents first. External context close behind. Longer tasks underneath. That is the important part. If this were only AI hype, I would expect LLM calls to dominate. They do not. LLM Call is at 8.8%. Instead, the dominant pattern is agent, external context, longer task, async lifecycle, scheduled return. That is much more useful than saying people are using AI. An agent without context is weak. It can answer, but it is mostly trapped inside a prompt. HTTP gives it the outside world. Long-Running HTTP gives it room for work that does not fit into one instant response. Async Commitment and Settlement give that work a lifecycle. Scheduler gives it time. This is the thread across the last few weeks. Week 1 asked: can contracts see outside? Week 2 asked: can agents become a real primitive? Week 3 asked: can these primitives start forming a stack? Week 4 asked: can async execution become the rhythm? Week 5 is starting to answer: yes, this pattern is repeating. The autonomous agents page adds another layer: 58 agents registered, with 33 Persistent and 25 Sovereign. That matters because the Sovereign Agent precompile number is not floating alone. There is already an agent surface forming. Persistent agents point toward longer-lived identity and state. Sovereign agents point toward execution participants. The base layer is active too: 37 validators, 37 active proposers, and 532 blocks analyzed in the last two minutes. I would not treat short live chart windows as final benchmark numbers. They move quickly. But they do show rhythm: blocks moving, gas usage changing, block sizes shifting, and execution that is not flat. The mempool snapshot also helps. Pending transactions are low. The scheduled pool is empty. The async pipeline shows 13. That async pipeline matters for product design. If Ritual apps use async workflows, users cannot be left staring at loading. They need to know where the work is: submitted, committed, settled, delivered, expired, or failed. A normal dApp can often pretend everything is one transaction. A Ritual app cannot. The workflow itself has to be visible. So Week 5 is not a totally new story. That is exactly why it matters. The same pattern keeps showing up. Transaction types show scheduled and async activity making up most of the window. Precompiles show Sovereign Agent, HTTP, and Long-Running HTTP leading. Agent stats show registered Persistent and Sovereign agents. Validator stats show live base-layer activity. Mempool shows not only pending transactions, but an async pipeline. The conclusion is pretty clear. Ritual testnet is not only being used as an EVM chain. It is being tested as a workflow environment. That is the important distinction. A normal chain is mostly about transactions. Ritual is starting to show another pattern: transactions start work, agents add execution, HTTP adds context, long-running calls add time, Scheduler brings work back later, async commitment and settlement give the process a lifecycle, and DKMS prepares the access layer. This is still early. The windows are small. The numbers can move quickly. But as a Week 5 signal, it is meaningful. Not because one metric exploded. Because the pattern survived another week. Not only transactions. Workflow behavior. Check: explorer.ritualfoundation.org/stats @ritualnet @ritualfnd
Meison (❖,❖)@meison_mswen

Ritual Stats: Week 4 Week 4 feels like the agent week again. But this time the story is stronger than “Sovereign Agent is on top.” Sovereign Agent leads the precompile table with 29.5%. HTTP Call is close behind at 26.5%. Long-Running HTTP follows at 15.8%. That already says a lot. Builders are not only testing whether contracts can reach outside the chain anymore. They are moving toward the bigger question: can agents actually execute inside the workflow? That is the shift. HTTP still matters because agents need context. Long-Running HTTP still matters because real tasks take time. But Sovereign Agent on top means builders are now touching the primitive that makes Ritual feel different. The transaction types make the pattern clearer. EIP-1559 is 36.10%, so normal EVM activity is still there. Contracts are being deployed, functions are being called, and interfaces are being tested. But the rest of the window is where the Ritual-specific behavior shows up. Scheduled is 10.66%. Async Commitment is 21.13%. Async Settlement is 32.11%. Together, scheduled and async activity make up around 63.9% of this window. That is the real Week 4 signal. More than half the activity is not just regular transactions. It is jobs, commitments, settlements, scheduled execution, and results coming back later. A normal transaction is a moment. An async workflow is a process. Week 1 was mostly about external data. Week 2 showed agents starting to matter. Week 3 looked like builders were climbing the stack: HTTP, Long-Running HTTP, Sovereign Agent, DKMS, LLM, media, ZK. Week 4 feels like those pieces are starting to behave more like a system. Sovereign Agent leads. HTTP stays close. Long-Running HTTP keeps the time layer visible. LLM and DKMS both show real usage. ZK, audio, video, and FHE are still smaller, but present at the edge. That is a healthy testnet pattern. Not every primitive needs to dominate immediately. Some primitives first appear as small signals before they become normal. The thing I like most here is not one number. This does not look like random clicking. It looks like builders testing how work actually moves through Ritual. Workflow behavior. Check: explorer.ritualfoundation.org/stats @ritualnet @ritualfnd

English
40
7
142
2.4K
MarvelCrypt | 3D Motion Designer (❖,❖)
Guess who's on Today's News again this new week Don't call yourself a ritual maxi if you are not Building, testing, bull posting and/or connecting Stay ritualised fams💚
MarvelCrypt | 3D Motion Designer (❖,❖) tweet media
English
2
0
11
68
UJ
UJ@Ukj1111·
Really happy that you liked it @CrypSaf ❤️ The box comes with two ears too that link magnetically to the face. They are fragile so we keep them nicely tucked in. One interesting trivia is that the ears used to be a part of the bloky when we made the first prototypes last year. However we realized that they had a tendency to break while shipping so we had to change the mould and that minor fix delayed production by 6-8 weeks Fast forward now, we have found another premium material that we can use to make it more sturdy and part of the same mould. However people like fidgeting with the magnetic ears so much that its becoming like a cool feature of the collectible now 🙂
SafZ@CrypSaf

I have a new guest My @OriginalBlokyz has arrived It took around 7 days to receive it. High quality packaging, loved it ❤️ The toy itself weights around 0.5kgs Good magnet so it can stand by itself Great experience 👏🏻 (Drop the NFT collection asap)

English
53
12
198
7.9K