RE: RE: Some announcements and AMA for a further CryptoBrewMaster plans
You are viewing a single comment's thread from:

RE: Some announcements and AMA for a further CryptoBrewMaster plans

RE: Some announcements and AMA for a further CryptoBrewMaster plans

Are you referring to api.hive-engine.com "the button" and "blocking"? That is one person's api node - and yes, he does have control over that one node. Anybody can create an api node. There are other public api nodes available

Maybe nobody tried to lie, but we get conflicting stories and strange, vague explanations as to why US customers are being put in this position. If you want to fix it - be clear. What is this button that you reference? geng only mentioned the difficulty using one of the available api nodes, but we repeatedly hear c24 representatives refer to the hive engine chain as centralized, or that it "has a button in the hands of their team". The closest thing I can think of is that they own the SWAP.* namespace for tokens, but that doesn't make any sense for what you're saying

you can store them in the Aeneas wallet or Sapien wallet which is noncustodial as well

Being able to withdraw tokens to a chain instead of an CEX would be a much better solution. A huge part of the issue is you've replaced a decentralized blockchain with a CEX - not just any CEX, but your CEX. At the same time, we're getting vague statements, conflicting statements, and USA customers being put in a very bad position

You clearly understand that multi-chain is the way. You are very correct about that. However, if the c24 team is going to drop a chain every time they have difficulty with a single api node, then my confidence isn't being bolstered. Players would be constantly trying to figure out how to not lose tokens abandoned on no-longer supported chains. This is why knowing what is happening matters

For me, a good solution would involve disclosing the technical reasons support for a chain is being dropped (they'd have to be really good. Multi-chain is the way). Not just "we got an error", but what error? What actually happened?

H2
H3
H4
3 columns
2 columns
1 column
Join the conversion now