[ANN][SHIFT] The New Web | IPFS/Phantom | ShiftNrg.org Hosted Decentralized!

[ocminer]

Those Orphans aren't a  problem of the network, I have them on the pool too, its pretty normal with those quick block times...

[ShiftTeam]

Those Orphans aren't a  problem of the network, I have them on the pool too, its pretty normal with those quick block times...

Exp has 60 seconds. Same there. This is a new issue. Not seen it before. But if people dont care about the stale blocks all of you can continue as normal on ocminers pool. We rather see that you solo mine to help secure the network.

[ShiftConnect]

Now it is clear
 Could you add  explanation to official page? All users should be able to find information quickly without mess and untrusted atmosphere. That the way how panic behave.

Best wishes,

We won't be putting up a permanent statement until we know exactly what's causing the issue.

We will however monitor the network and the thread closely for the time being.

[ocminer]

Those Orphans aren't a  problem of the network, I have them on the pool too, its pretty normal with those quick block times...

Exp has 60 seconds. Same there. This is a new issue. Not seen it before. But if people dont care about the stale blocks all of you can continue as normal on ocminers pool. We rather see that you solo mine to help secure the network.

They try to have 60 but it is rather 20 or 30 mostly. 

You will never have any stales or orphans -  with or without pool

[dygus]

edit: Why you doesn't make one more pool to split the hashrate?

He's right there should be at least one more pool.

EDIT: Next time inform community first, when you ask pool operator to shut down pool of any reason.

[Madmach]

Mining Pool source code was released:
http://cryptomining-blog.com/5800-weipool-has-released-the-source-of-their-ethereum-mining-pool/

[Teka]

Mining Pool source code was released:
http://cryptomining-blog.com/5800-weipool-has-released-the-source-of-their-ethereum-mining-pool/

For the sake of the network and decentralisation, I would be more than happy to help with graphic design and html/css of any new pool created specifically for Shift (Free of charge)

[defaced]

Those Orphans aren't a  problem of the network, I have them on the pool too, its pretty normal with those quick block times...

Exp has 60 seconds. Same there. This is a new issue. Not seen it before. But if people dont care about the stale blocks all of you can continue as normal on ocminers pool. We rather see that you solo mine to help secure the network.

They try to have 60 but it is rather 20 or 30 mostly. 

You will never have any stales or orphans -  with or without pool

maaaan I wish it was 30 again, its mostly 3-4 mins now. In the last 1000 blocks we have had 2 stales though. so :/

Which has alot to do with how the difficulty retargets in eth.

[ShiftTeam]

Those Orphans aren't a  problem of the network, I have them on the pool too, its pretty normal with those quick block times...

Exp has 60 seconds. Same there. This is a new issue. Not seen it before. But if people dont care about the stale blocks all of you can continue as normal on ocminers pool. We rather see that you solo mine to help secure the network.

They try to have 60 but it is rather 20 or 30 mostly.  

You will never have any stales or orphans -  with or without pool

maaaan I wish it was 30 again, its mostly 3-4 mins now. In the last 1000 blocks we have had 2 stales though. so :/

Which has alot to do with how the difficulty retargets in eth.

Nice to see you here. Yeah.. the difficulty adjustment takes time ok good to hear that you have fewer stale blocks. Thinking about raising the blocktime. I get a feeling that the blockdata does not have the time to propagate fully between mined blocks.

Regards

[Gumbork]

damn i missed all the dump, damn people should keep on dumping!!

[defaced]

Those Orphans aren't a  problem of the network, I have them on the pool too, its pretty normal with those quick block times...

Exp has 60 seconds. Same there. This is a new issue. Not seen it before. But if people dont care about the stale blocks all of you can continue as normal on ocminers pool. We rather see that you solo mine to help secure the network.

They try to have 60 but it is rather 20 or 30 mostly.  

You will never have any stales or orphans -  with or without pool

maaaan I wish it was 30 again, its mostly 3-4 mins now. In the last 1000 blocks we have had 2 stales though. so :/

Which has alot to do with how the difficulty retargets in eth.

Nice to see you here. Yeah.. the difficulty adjustment takes time ok good to hear that you have fewer stale blocks. Thinking about raising the blocktime. I get a feeling that the blockdata does not have the time to propagate fully between mined blocks.

Regards

That was my concern also, which is the main motivator for me to raise the blocktime. Gustav Simonsson pretty much called me a moron for doing so, and Vitalik said "it doesnt matter if its inefficient", but the fact is, there is a limited amount of stales that can go in the chain as an uncle and higher blocktime target just makes ghost that much more effective. Is 30 seconds good, is 60 seconds good, or is bitcoins 10 mins good? I'm not certain but a good starting point for me was 1 min due to my experience running FRK which is 30 seconds. They however said that my previous experience was invalid because I didnt write a blog post about it giving simulations and lots of fuzzy feelgood fluff. Even though blocktime has been discussed on this forum since this forum was first made.

[spartak_t]

That was my concern also, which is the main motivator for me to raise the blocktime. Gustav Simonsson pretty much called me a moron for doing so, and Vitalik said "it doesnt matter if its inefficient", but the fact is, there is a limited amount of stales that can go in the chain as an uncle and higher blocktime target just makes ghost that much more effective. Is 30 seconds good, is 60 seconds good, or is bitcoins 10 mins good? I'm not certain but a good starting point for me was 1 min due to my experience running FRK which is 30 seconds. They however said that my previous experience was invalid because I didnt write a blog post about it giving simulations and lots of fuzzy feelgood fluff. Even though blocktime has been discussed on this forum since this forum was first made.

Make it 5.5 mins by tomorrow, because seems like your daughter has something like an anniversary... it might help. After all.. smart people know that truth can be found with sharing and discussions, not by bashing other people's opinions.

[dygus]

That was my concern also, which is the main motivator for me to raise the blocktime. Gustav Simonsson pretty much called me a moron for doing so, and Vitalik said "it doesnt matter if its inefficient", but the fact is, there is a limited amount of stales that can go in the chain as an uncle and higher blocktime target just makes ghost that much more effective. Is 30 seconds good, is 60 seconds good, or is bitcoins 10 mins good? I'm not certain but a good starting point for me was 1 min due to my experience running FRK which is 30 seconds. They however said that my previous experience was invalid because I didnt write a blog post about it giving simulations and lots of fuzzy feelgood fluff. Even though blocktime has been discussed on this forum since this forum was first made.

Make it 5.5 mins by tomorrow, because seems like your daughter has something like an anniversary... it might help. After all.. smart people know that truth can be found with sharing and discussions, not by bashing other people's opinions.

Can we focus on developing shift coin as a primary goal?

[GoldenEye]

Exception and quick exit in the ShiftWallet GUI after creating a transaction:

Code:

ERROR   [src/bigint.cpp, #975; Vin] BigInt::Ulong value too big: 
i_unit              = 139786716497760, 0x7f22a194c760
BASE2               = 1000000000, 0x3b9aca00
MAX_UNIT_VALUE      = 4611686018427387903, 0x3fffffffffffffff


ShiftWallet: src/bigint.cpp:978: BigInt::Vin::Vin(BigInt::Ulong): Zusicherung »i_unit < BASE2« nicht erfüllt.
Abgebrochen

The transaction was sent successfully (tx shown in console), but ShiftWallet was immediately closed.

The same behavior in the Soil GUI

EDIT: current github sources, Linux x64, QT5.5

[spartak_t]

Can we focus on developing shift coin as a primary goal?

It is on topic in case you are wondering.

[123sss]

why such steep developer this coin has a small volume on TREX?

[ShiftTeam]

Exception and quick exit in the ShiftWallet GUI after creating a transaction:

Code:

ERROR   [src/bigint.cpp, #975; Vin] BigInt::Ulong value too big: 
i_unit              = 139786716497760, 0x7f22a194c760
BASE2               = 1000000000, 0x3b9aca00
MAX_UNIT_VALUE      = 4611686018427387903, 0x3fffffffffffffff


ShiftWallet: src/bigint.cpp:978: BigInt::Vin::Vin(BigInt::Ulong): Zusicherung »i_unit < BASE2« nicht erfüllt.
Abgebrochen

The transaction was sent successfully (tx shown in console), but ShiftWallet was immediately closed.

The same behavior in the Soil GUI

EDIT: current github sources, Linux x64, QT5.5

Lucky you that the author of that wallet is a part of Shift dev team. Hes looking into it right now.

[ShiftTeam]

[dygus]

Great news, thanks

[ShiftTeam]

Everyone needs to update to 0.4.0 as soon as possible. It is very important. All core nodes are updated.

Kind regards

https://github.com/shiftcurrency/shift-executables/tree/master/shift-v0.4.0