It's in the Ocean Planet chat (unless they edited or deleted it). I think the username was geng? something like that. Stated that the reason c24 team would not consider using a node other than api.hive-engine.com (it's really only useful for supporting old and slow sites, not dapps) instead of one of the better performing public api nodes run by the other witnesses (with fewer limitations) or standing up their own api is because they'd rather focus on making games than figuring out which api nodes to use. Having a variety of api nodes available and having the ability to stand up your own is a core part of decentralization. To say that you will not use any technology that allows you to choose different api nodes means you won't be using anything that allows for decentralization. By definition, if there is only 1 api node and nobody else can make one, that is a centralized system. According to geng, this is the only kind of system c24 wants to work with
look, HE is layer 2 with a button in hands of their team, they already blocked us twice, we got sick of this(
all the tokens are heading to another chain, if you don't want to store them in-game or on c24, you can store them in the Aeneas wallet or Sapien wallet which is noncustodial as well.
We plan to launch tokens on different chains and consider our launch on the SPK network as soon as they are ready.
nobody tried to lie, geng doesn't speak English well, and there was some kind of a language barrier)
But even in that case, he didn't mention that he loves centralization, in that way we wouldn't be a part of the Hive community for years and didn't hold our proxy stake)
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?
ah - here it is. By "locks" he was referring to that time before the chain was decentralized when c24 was on the "exchange" list and couldn't receive tokens. It's decentralized now, so witnesses would have to agree to an alteration to the smart contract to make that happen today. Very different situation than before. After talking about that, he went on to the rate limiting on mancer's api node
This is really a big misunderstanding. If rate limiting was the problem and if that node was creating issues. We have a bunch of other nodes for Hive Engine that can be used. You can have your own node too for your tasks. The data is going to be anyways on-chain. If you have challenges in creating and maintaining a node, I also offer that as a service. You can contact me.
It is also not a hard task to create an intermediate app that will rotate nodes based on availability. I have done that for my apps as well. Also, this is a blockchain feature and not something specific to Hive Engine alone. @rollie1212.
Hive will also have a similar concept. That's why people rotate their nodes and use them. If it is blockchain, this concept is very common.
It's in the Ocean Planet chat (unless they edited or deleted it). I think the username was geng? something like that. Stated that the reason c24 team would not consider using a node other than api.hive-engine.com (it's really only useful for supporting old and slow sites, not dapps) instead of one of the better performing public api nodes run by the other witnesses (with fewer limitations) or standing up their own api is because they'd rather focus on making games than figuring out which api nodes to use. Having a variety of api nodes available and having the ability to stand up your own is a core part of decentralization. To say that you will not use any technology that allows you to choose different api nodes means you won't be using anything that allows for decentralization. By definition, if there is only 1 api node and nobody else can make one, that is a centralized system. According to geng, this is the only kind of system c24 wants to work with
look, HE is layer 2 with a button in hands of their team, they already blocked us twice, we got sick of this(
all the tokens are heading to another chain, if you don't want to store them in-game or on c24, you can store them in the Aeneas wallet or Sapien wallet which is noncustodial as well.
We plan to launch tokens on different chains and consider our launch on the SPK network as soon as they are ready.
nobody tried to lie, geng doesn't speak English well, and there was some kind of a language barrier)
But even in that case, he didn't mention that he loves centralization, in that way we wouldn't be a part of the Hive community for years and didn't hold our proxy stake)
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
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?
What do we do with left over ash in hive Engine now?
ah - here it is. By "locks" he was referring to that time before the chain was decentralized when c24 was on the "exchange" list and couldn't receive tokens. It's decentralized now, so witnesses would have to agree to an alteration to the smart contract to make that happen today. Very different situation than before. After talking about that, he went on to the rate limiting on mancer's api node
This is really a big misunderstanding. If rate limiting was the problem and if that node was creating issues. We have a bunch of other nodes for Hive Engine that can be used. You can have your own node too for your tasks. The data is going to be anyways on-chain. If you have challenges in creating and maintaining a node, I also offer that as a service. You can contact me.
It is also not a hard task to create an intermediate app that will rotate nodes based on availability. I have done that for my apps as well. Also, this is a blockchain feature and not something specific to Hive Engine alone. @rollie1212.
Hive will also have a similar concept. That's why people rotate their nodes and use them. If it is blockchain, this concept is very common.
https://beacon.peakd.com/