[ANN] Fantom | CPU Mineable | DarkSend | Masternode | Tor+I2P | sMP Releasing Sn

[quantumgravity]

Okay, so I went on a fork for like two hours. I think it was because my weight was too high so I've split my balance between a few computers to try and stop that problem from happening again.

[joshafest]

I am getting a ton of orphans staking - like 60% or more. Is it a problem with the difficulty or what? Or is it because the block times are so quick? Probably a bit of both? DuckYeah! I remember you mentioning switching to 90 second blocks if you decide to implement a more robust algorithm. That may be a good solution.

have you updated wallet?

[MisO69]

Has someone got a GPU miner already?

One miner on coinspool running at 10x the hash of everyone else with quite a few invalid shares

Either they are running multiple cpu miners (160 cores equivalent by my estimate) or they have created a gpu miner and are not sharing

Just asking as that one address has quite a large % of the network hash

Nobody would bother making a GPU miner for this coin. There is no volume and hardly any buy orders on c-cex. Seems to be the general state of crypto at the moment.

[quantumgravity]

I am getting a ton of orphans staking - like 60% or more. Is it a problem with the difficulty or what? Or is it because the block times are so quick? Probably a bit of both? DuckYeah! I remember you mentioning switching to 90 second blocks if you decide to implement a more robust algorithm. That may be a good solution.

have you updated wallet?

Yes I have the latest release.

[quantumgravity]

Fantom has been added to blocktree.io block explorer

http://www.blocktree.io/e/FNX

Rich List: http://www.blocktree.io/richlist/FNX

Nodes (with addnodes): http://www.blocktree.io/peers/FNX/

Donations welcome to:

FnHMySHDZxvp2qDv7pQ6eUifBq1YZtRLho

Great job, thanks! I sent a small donation for your efforts.

[joshafest]

I am getting a ton of orphans staking - like 60% or more. Is it a problem with the difficulty or what? Or is it because the block times are so quick? Probably a bit of both? DuckYeah! I remember you mentioning switching to 90 second blocks if you decide to implement a more robust algorithm. That may be a good solution.

have you updated wallet?

Yes I have the latest release.

still have issue....is connection to internet alright? ....i mean to say it will reject block because of internet not working properly .
if it is all well then  will have a look over sorce.
i think some tests still left over new pos schem pherhaps.
please let me know if internet working properly.

[quantumgravity]

I am getting a ton of orphans staking - like 60% or more. Is it a problem with the difficulty or what? Or is it because the block times are so quick? Probably a bit of both? DuckYeah! I remember you mentioning switching to 90 second blocks if you decide to implement a more robust algorithm. That may be a good solution.

have you updated wallet?

Yes I have the latest release.

still have issue....is connection to internet alright? ....i mean to say it will reject block because of internet not working properly .
if it is all well then  will have a look over sorce.
i think some tests still left over new pos schem pherhaps.
please let me know if internet working properly.

It must be something with the pos in the code. My internet connection is consistent and hardwired up to 120 Mbps download and 25 Mbps upload speeds.

[joshafest]

ok give me some time ...to look.

[DuckYeah!]

This is to inform that to use Birthday Hash Collisions, the block has to be entirely restructured (a.k.a. When validating, invalidating the previous blocks thus holding the client useless to validate older blocks).

A Swap may be imminent, what is your say if a swap were to take place

[quantumgravity]

This is to inform that to use Birthday Hash Collisions, the block has to be entirely restructured (a.k.a. When validating, invalidating the previous blocks thus holding the client useless to validate older blocks).

A Swap may be imminent, what is your say if a swap were to take place

Would a swap be necessary? Couldn't you just release a mandatory wallet update that forks the code with the upgraded algorithm? It might be easier and less messy than a swap.

[joshafest]

This is to inform that to use Birthday Hash Collisions, the block has to be entirely restructured (a.k.a. When validating, invalidating the previous blocks thus holding the client useless to validate older blocks).

A Swap may be imminent, what is your say if a swap were to take place

swap is not neccessary....please...update wallet .

[quantumgravity]

ok give me some time ...to look.

Cool, thanks!

[DuckYeah!]

This is to inform that to use Birthday Hash Collisions, the block has to be entirely restructured (a.k.a. When validating, invalidating the previous blocks thus holding the client useless to validate older blocks).

A Swap may be imminent, what is your say if a swap were to take place

Would a swap be necessary? Couldn't you just release a mandatory wallet update that forks the code with the upgraded algorithm? It might be easier and less messy than a swap.

Well, a block has x amount of elements, now the new design makes it x+y (z) so when it has to verify blocks with design x, it will try with z being the factor and x doesn't equal z , therefore invalidating blocks. I said I will try to avoid swap because of the stuff and work involved, but I am trying to avoid this problem

[quantumgravity]

This is to inform that to use Birthday Hash Collisions, the block has to be entirely restructured (a.k.a. When validating, invalidating the previous blocks thus holding the client useless to validate older blocks).

A Swap may be imminent, what is your say if a swap were to take place

Would a swap be necessary? Couldn't you just release a mandatory wallet update that forks the code with the upgraded algorithm? It might be easier and less messy than a swap.

Well, a block has x amount of elements, now the new design makes it x+y (z) so when it has to verify blocks with design x, it will try with z being the factor and x doesn't equal z , therefore invalidating blocks. I said I will try to avoid swap because of the stuff and work involved, but I am trying to avoid this problem

I guess I see your point. Whatever solution is best for the coin, the network, the stakeholders, and the community is what we should pursue.

[quantumgravity]

Is I2P active? Will it work if I activate it in the wallet?

Edit: Or will I2P and Tor be operational for the Jelly Head release?

[DuckYeah!]

I2P works, but there need to be peers

[ethought]

I vote FNX too..

[drizzle2405]

Make sure to check your wallet.  I just so happened to not check my client for a day and happened to be on the same fork that quantum went on.  There were at least 3 other solid connections on the same fork....

[quantumgravity]

Make sure to check your wallet.  I just so happened to not check my client for a day and happened to be on the same fork that quantum went on.  There were at least 3 other solid connections on the same fork....

Yea I had a few other connections on that fork, so be vigilant. Exit and restart your wallet every now and then just to be safe or check with the block explorers to see if the block height matches.

[Bavaria]

The dev of this coin has very unserious name.