Are you able to provide a break down of the high level tasks to completion, and how many AZ submissions/phases you anticipate you will need?
Would love to see this proposal get up
Are you able to provide a break down of the high level tasks to completion, and how many AZ submissions/phases you anticipate you will need?
Would love to see this proposal get up
It’s difficult to answer this because the price keeps going down and the costs keep going up. Honestly we stopped looking at the hours we’re putting in because it was becoming a bit disturbing. Like it seemed irrational to keep doing things.
Imo for such a critical piece of infra its fair to ask for multiple grants à 5k ZNN / 50k QSR, especially at these prices.
I guess what the community would appreciate is to get a rough understanding for how many of these full grants you’re gonna ask.
Maybe it could make sense to say e.g. 2 for the first bridge implementation, and then maybe 1 for the next 2 additional bridges, and 0.5 for every subsequent ones. Up to you to define what would feel “fair” for you guys considering what counts are solutions rather than hours.
This would allow the community to give you grants for clear deliverables instead of work in progress.
Just an idea
There will certainly be clear deliverables starting with the next phase.
Can you already post a list? This would help lobby for your current AZ proposal
Sir, my question is similar to @cryptocheshire’s in that I’m just wondering how many phases we can expect and the approximate timeframe. I know that is hard to predict now. But we had a wallet project presented, approved, completed, and funded without a clear path to full completion. The wallet needs multiple full submissions, but that was not 100% clear initially.
Maybe as Shazz discussed, you can break things into 2 to 4 milestones that could fit nicely into AZ submissions. Just a 30,000’ roadmap in a few words each.
Are you involved with THORchain in any way?
How many bridges have you developed?
Thank you sir for you submission and time!
We’re still in discovery mode with the roadmap and the deliverables, but we’re hoping to clarify most of them this month. As soon as we have more to share we’re going to publish an update.
OK. I will vote yes on this proposal. Just please understand that we are sensitive to developers requesting funds for projects that do not have a clear path to deliver the entire project.
thank you!
Like you should.
Thank you for your vote!
I voted yes because of your pfp
Actually fair game. A nicely branded anon dev probably delivers a nicely branded cross-chain bridge.
Sounds very promising, hopefully this project sees fruition. If you need testers i’ll gladly QA it.
Hello Aliens,
Reporting to the Mothership:
I’m excited to announce that the Multiverse project is hitting an important milestone: the release of the open beta.
The community is invited to test the bridge that is currently setup to support bidirectional swaps between Zenon Testnet and Ethereum’s Goerli Testnet.
For more transparency requested by community members, I’ve also compiled a short FAQ regarding the current status of the project.
How can I test the bridge?
Thanks to @dexZNNter, the bridge frontend is available here:
Where can I get tokens to test it?
You can get testnet tokens from the following sources:
Zenon Public Testnet faucet:
@znn_faucet_bot
ETH Goerli faucet:
Where can I report an issue?
You can report issues in this thread.
What about the security of this bridge?
The bridge is designed with a multi-layer security architecture in mind and additional security modules for the bridge are currently in development. Although we make huge efforts, there are always ways to enhance the security. We will perform internal security reviews, but an external security audit should be conducted before the official launch. The bridge has 3 main components that will require to be audited: the Solidity smart contracts, the core module and the Zenon embedded contract.
What else can I do to help?
Beside testing it, spreading the word about this project beyond Zenon’s community is also equally important. In this way, other projects can hear about it and provide additional support.
Please consider that this project is still under heavy development, so expect things to break and kindly report only valid and reproducible issues.
We will keep you updated with the progress.
Buckle up for the official launch!
Brave Browser, Ubuntu 22.04
Refreshed 3x. It finally worked. I was not able to inspect fast enough to see any issues.
My computer is doing PoW to get more test ETH, so that could be the issue.
How long does it normally take to do the bridge? Does the computer need to do PoW to complete the TX?
On first attempt, the bridge worked exactly as expected. I need more testETH. Will keep playing with it and report back.
I wonder if we can improve the appearance of this page. The transaction looks strange in that window.
I tried to unwrap wZNN to ZNN. While the “Signing” process was taking place (to unwrap the token), I tried to wrap ZNN to wZNN. That seemed to remove the Unwrap Request all together and execute the ZNN to wZNN request only.
After making the request to Unwrap the wZNN
After making the request to wrap ZNN to wZNN
After 90 seconds or so this reappeared
Is this behavior expected?
I just converted wZNN to ZNN
The wZNN was removed from my wallet and hit syrius, but it’s still showing up as a redeemable asset a few minutes after the tx in the bridge
I tried to redeem the 69 a second time (an attempted double redeem) and now syrius is stuck “Sending” the TX for a few minutes. I will let it run to see if it times out.