PM me your debug.log if possible.

Practically, as much as needed. The upper bound is probably somewhere around 1M TPS though. Also, it strengthens the core PoS algorithm and provides more security guarantees. We'll also support smart contracts and dynamic state execution.

Our blockchain will be the best possible blockchain people can use. We're implementing sharding to achieve quadratic scaling (as many TPS as needed basically) and a unique on-chain code governance feature where blockchain updates can be carried out without updating any core code through a community vote.

We aren't linked to Nigeria at all...


I will hopefully keep working on Synapse for a long time. The main net will be ready in a few months probably.

It won't take years. I'm guessing it will take a few months to get everything setup and stable.

2 masternodes.


It can be possible on decentralized exchanges too but there's not any reason for inflation on decentralized exchanges.

This is almost completely illegal wash trading and volume inflation by IDAX. We have no control over it unfortunately. IDAX wants to inflate their volume to charge high listing fees.

We're aiming to do this. Unfortunately, we just don't have the money for exchange listings.

Synapse update:

wqking has been working on implementing a new peer discovery system for the testnet (very similar to Bitcoin's system).

I've been working on getting shard code executing and some basic functions implemented. Currently, shards can store/load from storage and verify ECDSA signatures. I'll add hashing soon so that shards can calculate hashes. The transfer shard (allowing transferring Phore from one user to another) will be built off of these operations. Once we have the transfer shard done and the governance shard, we'll launch the main net of Phore Synapse.

You can see what the low-level smart contract code looks like here: https://github.com/phoreproject/shards. Any language that compiles to WebAssembly will be compatible.

Will likely be more than 30 days. I said the beacon chain will be up and running. There are still a few more major tasks before the main net.

The errors in the Synapse testnet were mainly due to peer discovery and network connectivity. We'll have the updated system ready by Friday to test again Monday probably.

Starts at 11 PM PST actually. Unix timestamp: 1557900000


Chain upgrade on the testnet. The main net is not affected. (yet)

No. This is just a testnet. It does not affect the current mainnet in any way, but it will be evidence of the work we've been doing for the past 6 months.


Probably not, because Phore is a very low cap coin with lots of slippage. However, the new architecture does show evidence that we're doing much more work than projects priced similarly.

Note that this is just a testnet for the new architecture. We aren't updating the network yet. We're just testing part of the new architecture by mining empty blocks.

We're going to build a great blockchain that people want to use/buy. This also goes for exchanges. Exchanges will add us, not because we pay them, but because their users want to trade Phore.

They may use our implementation of BLS and we're using their serialization/hashing library (ssz). https://github.com/phoreproject/bls/issues/5


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.


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/synapse


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.


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)


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.


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/).

There is no transfer mechanism yet. This is because we're just testing the consensus mechanism (basically mining empty blocks). However, it's extremely important to test this so that we have a stable base to build dApps and actually useful shards on.

That being said, we do have a block explorer that will be released soon for Synapse. This will let the community view different aspects of the beacon chain. Also, the beacon chain doesn't track balance transfers at all. The only job of the beacon chain is to process attestations, crosslinks and CASPER. Our shard chains will handle everything else (transfer, governance, privacy, smart contracts).


No updates to the main chain yet. We're still testing the new architecture.

LOL... That is not true at all. We're launching our testnet about the same time they're launching theirs. This includes only the beacon chain which is the consensus mechanism and runs CASPER/attestations. I'm collecting public keys for validators for the testnet now from volunteers from the community. I'll finish this process Friday. Then, we'll start the testnet sometime next week (most likely Tuesday 9 PM PST if all goes to plan). This testnet includes beacon chain block proposals, attestations, CASPER.

Prysmatic's beacon chain does not run on multiple nodes yet (single client as stated in their release). Ours is multiclient. Also, they don't have attestation sharing through their P2P network. We do. Finally, I believe they're using Phore's code (specifically the BLS library) in ETH Serenity (2.0): https://github.com/phoreproject/bls/issues/5. Phore Chia, Algorand, and ETH are working with cryptographers to finalize an IETF document standardizing BLS signature implementations.

I'm also working currently on getting a block explorer up and running so that the public can see the testnet beacon chain progress and validate attestations.

Can you please point it out? Here's a diff of Phore headers vs. PIVX headers. Thanks! I'd like to get this resolved.

https://gist.github.com/meyer9/4b343d1005fea1e8c70d643a33543c83

I realize in the past, Phroshi made the mistake of changing PIVX to Phore in the license instead of adding Phore under PIVX to give both credit. Although this was probably intentional, it was almost certainly not malicious. In addition, it was fixed over 2 months ago in this commit: https://github.com/phoreproject/Phore/commit/e0fc7765fdcf276ee2be9409974bd2c7125c8b58. I don't understand why you are bringing it up now.

I'm sure this was not intentional. I have write-access to the repo so I can fix the licensing today.

EDIT: I just did a grep and I could only find one file where "MIT" was not mentioned. chainparamsseeds.h is auto-generated. Can you point out which header files we stripped the license from? I'd really like to resolve this issue. Thanks!

EDIT 2: I hope it wasn't intentional, I should say.

As a developer, I'd like to say that the code is under very active development with research being done now into smart contracts, side chains, atomic swaps, two-way pegging, and scaling.

Adoption is our number one goal and it starts with providing developers tools they need to write new applications to use Phore. We do not want our coin to be used because people are forced to use it. We want our coin to be used because it's the best solution to a problem.