@TelosUnlimited@HelloTelos@SnaxTeam I understand how it works. You run #Ethereum contracts on #Telos. However, these contracts do not live on Eth, in fact. You still need wrap a token to make it available on Ethereum natively, otherwise user will have to operate on Telos. Thx for the link anyway, I will join later.
@TheCircularCale@rektkid_@SnaxTeam If @block_one_ having $2B would bothered to build IBC in 3 years as per their roadmap, you could send any #EOS token to anyone by user nickname in #Twitter, for example. That's what Snax is about - a trustless protocol, links accounts on public social platforms to a blockchain.
@HelloTelos@SnaxTeam But people still need a separate wallet to use it. That's one of the problems with low-adoption chains, was a problem of Snax as well.
@HelloTelos@SnaxTeam Thanks for your invitation! #Telos community does good job. The problem is that Snax protocol can't work on Telos chain because of specific core, required for the social transactions mechanism. We're thinking about #Ethereum not because of EVM, but because of its wide ecosystem.
@rektkid_@SnaxTeam Current Snax implementation is built on the own fork of EOSIO engine. I explained in other replies why did we choose it and why we decided not to support this version of chain anymore.
@TelosUnlimited@SnaxTeam@HelloTelos @block_one_ #EOSIO is built on the old Steem codebase. Has tons of bugs, crashes on a high load. As engineers, we would never have chosen it for our protocol, if #EOS roadmap didn't include IBC. However, @block_one_ decided not to follow their roadmap.
@CaptainCryptoHD @SnaxTeam What's the point to support something on a dead engine? If haven't a chain, we have to change the model anyway. Current Snax implementation requires own chain and can't work on Telos because of specific core. If we decline the idea of own protocol, we can choose any ecosystem.
@CyptoGeneration@SnaxTeam One of the main problem of using non-Ethereum chain was the lack of good exchanges. They can't implement new protocols because most of them even have no engineers in-house. On #Ethereum, we could use @Uniswap or @Bancor at least. Ecosystem reduces costs.
@TelosUnlimited@SnaxTeam@HelloTelos EOS is dead. Honestly, @block_one_ fucked up everything. They made one more crappy social media (Voice) to satisfy Larimer's ambition instead of supporting EOSIO ecosystem or building IBC, at least.
We'd like to inform everyone that, sadly, we have to stop supporting Snax #blockchain in its current state. #EOS engine and its ecosystem are not progressing and we should review #Snax model to migrate it to #Ethereum or its sidechain.
@Maxocoin @finchify @EOSauthority In #Snax we've solved this problem by changing the cost function: it grows exponentially only for accounts, who made a large amount of transactions last 24h. So, each account is available to send about 10tx per 24h at least.
@Maxocoin @finchify @EOSauthority No, it doesn't. The relation between available CPU time for some account and its EOS stack is not a constant. Resource cost function grows exponentially with the total CPU usage, it doesn't distribute anything among accounts, just set something like 'CPU price' at the moment.
Announcing a new project: POWSWAP.
POWSWAP is a no-bullshit smart contract/platform for trading Bitcoin hashrate derivatives.
What does no Bullshit mean? No middlemen. No oracles. No escrows. Nothing but Bitcoin.
Sign up at https://t.co/x8EWtuFSfO.
Why is this a big deal?
๐กFortunately, in #Snax we rewrote the function, which is forming the $NET and $CPU price. Snax has a progressive function, which allows the user to send transactions at a lower cost, if their total transaction amount is small.
#EIDOS#attack#EOS#blockchain