Ethereum has huge security problems with smart contracts, with scalability and network stability.
If Phore manages to solve these problems, we expect a flight to the moon.
ETH2.0 team communicates with the PHORE team
I am sure that PHORE will soon show a steep price increase!
where did you get the information that the Phore team communicates with the ethereum team?
I think they have one goal, to create a flawless blockchain, but I have not heard about their cooperation.
it is quite possible, that it is. some team members have a high ranking in the field of cryptocurrency. so, this cooperation is possible. it is mutually beneficial. however, I would like a documentary or other visual confirmation
They may use our implementation of BLS and we're using their serialization/hashing library (ssz).
https://github.com/phoreproject/bls/issues/529 million transactions per second.
Is there a need for such a powerful payment system?
How did you calculate that there will be 29 million and not 1 million if your blockchain is still flawed?
This is an upper theoretical bound based on our current TPS (this assumes 400k shards, but there will likely be closer to 1000 to start based on economic calculations). 1000 shards should be about 70,000 TPS which is obviously plenty for now. Our blockchain is not flawed.
Synapse is an improved version of Sharding, which was used on the network ethereum?
I heard that all the synapse code is written from scratch. It's true?
Yes. We're writing it from scratch because there is no blockchain that supports sharding yet. We're working with ETH on the beacon chain because our design is similar to theirs, but the shard chains will differ greatly (more similar to Tezos than Ethereum). Here's the source code for the new design:
http://github.com/phoreproject/synapseHow will Synapse significantly improve a smart contract from the one that exists on the network ethereum?
I'll try to explain this in simple terms. Ethereum has rule sets for how state should transition from one block to the next (add/subtract balances, update contract state, etc). We're making these transitions dynamic and voteable by the community. If we want to add an opcode, for example, we can submit new code written in WebAssembly to the network. Network participants will vote on the hashes and approve installation of the new code, and the new code gets implemented without a wallet update. We're still figuring out details of this, but that's the basic idea.
Are you testing consensus now?
Does blockchain work stably when processing empty blocks?
Yes. I've been running a chain on my server for about a week with no stability issues. We're launching a testnet on Tuesday, May 14 which anyone will be able to connect to and sync with. (all of this is mining empty blocks)
Ethereum has huge security problems with smart contracts, with scalability and network stability.
If Phore manages to solve these problems, we expect a flight to the moon.
See my reply above, but we fix security problems through community governance. If the DAO hack had occurred on Synapse, the hard fork would not be decided by exchanges or developers, but would be decided by the community through our governance system. It's a more democratic and secure way of solving security issues.
Ethereum has huge security problems with smart contracts, with scalability and network stability.
If Phore manages to solve these problems, we expect a flight to the moon.
ETH2.0 team communicates with the PHORE team
I am sure that PHORE will soon show a steep price increase!
where did you get the information that the Phore team communicates with the ethereum team?
I think they have one goal, to create a flawless blockchain, but I have not heard about their cooperation.
it is quite possible, that it is. some team members have a high ranking in the field of cryptocurrency. so, this cooperation is possible. it is mutually beneficial. however, I would like a documentary or other visual confirmation
If there was cooperation, they would have announced this in their official blog.
I think they communicate with each other and share experiences, but no more than that.
We don't want to announce anything because Ethereum hasn't committed to using it, but they'll probably use our implementation of BLS for their Go client. I'm (Julian Meyer) also on the working group for the IETF BLS standardization effort (
https://datatracker.ietf.org/doc/draft-boneh-bls-signature/).
