As the number of chains increases, there seems to be a growing need for more resources to reduce our reliance on a single platform, like dbxen.org. I'm not alone in experiencing issues, particularly with the MATIC side of things. Notably, these challenges didn't exist before certain changes were implemented. (For those unaware there are two iterations due to said changes and I was in on the first day so I own both)

I've had private conversations with a member of the team, and it's apparent that resolving this has been a challenge. Considering these challenges, how would others approach this situation? I wonder if there might be a solution via the block explorer. However, I'm unsure if anyone has explored this option yet.

On a positive note, as I was drafting this post, I noticed that the team has addressed the problem I was previously experiencing (which was still present less than 24 hours ago). This swift response does boost my confidence in their ability to handle issues.

This is interesting, but too vague. What was the issue?

    EtherX
    Not my image this is from another user in the TG. You would just get stuck on this and you couldn't do anything about it especially if you didn't know any workarounds. (which is why I created this thread just in case something like this happens in the future) This is not a jab at the team nor is FUD they've done an amazing job despite some hiccups along the way.

        treebsOG
        Anticipating a scenario like this is why I created this thread:
        https://xen.pub/forum/d/14-request-video-tutorials-for-interacting-with-contracts-via-etherscanio

        Imagine it's time to claim a XENFT. You go to xen.network, but it 404s. Or there's some server side error. Or you see something similar to that screenshot that prevents you from claiming. You contact the team on TG, Twitter, Discord, email. 24 hours pass with no solution. The website is fixed several hours later, but you have lost 1% of your mint at no fault of your own.

        Due to how common and encouraged it is to use dApps through websites, I don't expect that many people know that you can interact directly with the smart contract by connecting your wallet to web3 on etherscan. For example, the XENFT contract is here https://etherscan.io/token/0x0a252663dbcc0b073063d6420a40319e438cfa59#writeContract

        I haven't tried this myself, but if I had to guess, you'd first have to call approve (0x095ea7b3) (https://etherscan.io/token/0x0a252663dbcc0b073063d6420a40319e438cfa59#writeContract#F2) and after that callClaimMintReward (0xdf0030ef): https://etherscan.io/token/0x0a252663dbcc0b073063d6420a40319e438cfa59#writeContract#F7

        I imagine there are functions that can be called on the DBXENFT and Xenon contracts. For DBXENFT, the contracts I see are

        1. https://etherscan.io/address/0x22c3f74d4aa7c7e11a7637d589026aa85c7af88a#writeContract
        2. https://etherscan.io/address/0xa06735da049041eb523ccf0b8c3fb9d36216c646#writeContract

        It's very confusing to figure out which contract to use. Only the first one has an approve function, but the second one is where most of the activity is. Both of them have a function named mintDBXENFT. This is where I hope the community can contribute by creating tutorials on which functions to call and in what order to complete various tasks.

        As for Xenon, I haven't redeemed any XENFTs yet using it, so I don't know what the contract address is (is there one? Raz said it interacts with traditional backend services so maybe not). A contract address is not available anywhere on app.xenon.tools or on the Starfish Technologies twitter. Apparently it is active on Mumbai testnet, but you can't even mint XENFTs on Mumbai. Someone please correct me if I'm wrong. I suppose one could mint a XENFT on a cheaper network to try to test the contract themselves, but everyone should really be able to test it on Mumbai, that's what testnets are for.

        I honestly don't know why this isn't talked about more. A community that embraces first principles should not be relying on a single point of failure.

            I'm not even sure about Xenon I forgot it existed until I saw someone post about it here. I think this place will be good on shedding light on subjects that have been discussed many times over. From my perspective if you're going to build onto XEN you should also allow people to self host their own front-end in case another goes down. That reason could be the one that Jack himself took into his own hands and gave the people a chain because XEN is immutable he considers it a finished project. RH has taken the approach where he tells people to go out there and build because it helps the entire community along with his tokens.

            treebsOG Clear the cache, Shift and F5, reset the internet router and will show up. Some people are so dumb that is out of mind 🙂

                treebsOG
                This is the error when this happens:

                The problem arises from the Moralis RPC utilized by DBXENFTs. It's primarily due to the constraints set by this RPC on the number of simultaneous information requests. This happens when everyone rushes in at 10 AM EST to check their DBXENF claims. For now, a simple solution is to wait for about 15-30 minutes or try refreshing the page.

                On a side note, I've verified with @razvancostin14 that an additional 1 million limit has been acquired from Moralis to address this challenge.

                    BitCode This is helpful to your average person and that's it. The original post wouldn't exist if it were that simple and not only that you're missing the entire point if you read the entire thread.

                    Admin Yeah I went through this same process with raz as well and pretty much knew it was an RPC issue as I've seen it happen with many other sites even on other chains. That's great to hear and all I'm just not a fan of Moralis for various reasons which I won't get into because it's off topic. If anyone could host their own front-end just as they can an RPC then all one would need is the code.. so unless I'm missing something there's a reason that's not the case here. If it's for security that's fine with me I just don't know and we may never know because at the end of the day it's a business for them so I understand that aspect of it.

                          treebsOG No need to read entire thread. Then change the RPC or create new one from your side and will work. RPC also having caching so this way or that way is very non sense problem that you are bringing here. Plus the third party issue is not in the reach of DBXEN team.

                              4 days later

                              BitCode We can just agree to disagree then that's fine. This is bigger than DBXENFTs and while I could create another topic it's still not going to solve the bigger picture. People can give CoinTool all the hate in the world but they did it right by showing people how to claim if the site just goes poof one day... every other XEN project should do the same IMO. If you or anyone else has a solution to that then feel free.

                              genesis_1_1_1 is onto something already and I think that's a great place to start.

                              Once this is figured out eventually then that gives us a template to apply to every other chain that XEN is on currently and in the future.