Alexandru Husaru @husaru

⚡️AI MEETS BLOCKCHAIN PAYMENTS AI just learned how to use a crypto wallet. MultiversX is the first blockchain to integrate Google’s Universal Commerce Protocol, letting AI agents check balances and execute on-chain transactions automatically.

192 469 1K 115K 80

View Details

Alexandru Husaru @husaru

6 months ago

@NicusorDanRO De ce nu există legislație unitară? Este de preferat pentru că oferă predictibilitate, echitate și stabilitate. Pe scurt, este esențială pentru ca două persoane aflate în situații identice să nu primească soluții opuse doar pentru că dosarele lor au ajuns la judecători diferiți.

0 0 3 702 0

View Details

Alexandru Husaru @husaru

8 months ago

@axelar @SasuRobert @MultiversX @axelar, everything OK? #MultiversX community is waiting...

0 0 4 137 0

View Details

Mihai @mihaieremia

8 months ago

Lost brothers from @axelar @Axl_Ecosystem @sergey_nog @JasonRozovsky @Elen__Kay @0xkeithhh @yorgosv_ Would you dare to speak on what is the blocking point for releasing the integration you've been promising to the @MultiversX community? I can see the work done on all ends as well as audits: github.com/search?q=org%3… I tested the devnet flow myself and reviewed the codebase; it's all there. What am I missing? What is blocking the release? Did other L1s pay you better to front-run other releases? Let's find a solution. Tell us what's missing, and I'll personally spend my nights getting the tech done if that's what's left. If the tech is done and it's just "paperwork," tell us what it's about, and we'll sort that out too. You, as a foundation, have bylaws to respect, especially if contracts were signed that a protocol wants to use your technology, invested money in building the integration and audits, and then at the end of the road, everything is stuck. Does that mean Axelar is not open for integrations? Is this a closed-loop layer where only if you're somebody can you get past the release line? I want to deploy a cool DeFi protocol on top of Axelar but guess what I can't because your protocol is not moving forward with the deployment... maybe we should have gone to the competition layer for an integration, pay the job, do the audits and have it done, we went with you and seems like you went on another path at the end of the tunnel.