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

Gumbork

hero member

Activity: 583

Merit: 500

Quote from: ShiftTeam on September 23, 2015, 11:15:13 PM

Quote from: P-Funk on September 23, 2015, 06:52:09 PM

Can you provide more details regarding this update? Is it a hard fork? If so, when, now? How/when will the block target change to 25 seconds happen?

Definitly not a hard fork. Nothing has changed in blockchain. The 25s target blocktime is running right now. Upgrade else your client will be out of sync.

thanks for the details dev, hopefully we get more dumpers to fill my buy orders.

ShiftTeam

hero member

Activity: 483

Merit: 510

The Shift Team

Quote from: P-Funk on September 23, 2015, 06:52:09 PM

Can you provide more details regarding this update? Is it a hard fork? If so, when, now? How/when will the block target change to 25 seconds happen?

Definitly not a hard fork. Nothing has changed in blockchain. The 25s target blocktime is running right now. Upgrade else your client will be out of sync.

NextGenCrypto

sr. member

Activity: 462

Merit: 250

Quote from: Billyboy402 on September 23, 2015, 09:46:35 PM

can we please activate hybrid PoW-PoS so it rewards early miner that haven't dump

That's actually a pretty good idea and would likely go a long way to encourage holding rather than selling.

Billyboy402

hero member

Activity: 599

Merit: 500

can we please activate hybrid PoW-PoS so it rewards early miner that haven't dump

Billyboy402

hero member

Activity: 599

Merit: 500

It was my own fault , I was running it from the EXE and not the bat file

Quote from: OzDigger on September 23, 2015, 09:38:12 PM

Quote from: ?? on ??

Why am i getting when trying to mine solo on 4.0
3.0 was working fine

Quote

JSON-RPC problem. Probably couldn't connect. Retrying in 1...
miner 12:31:24|main Getting work package...
X 12:31:25|main Failed to submit hashrate.
X 12:31:25|main Dynamic exception type: class jsonrpc::JsonRpcException
std::exception::what: Exception -32003 : Client connector error: libcurl error: 7 -> Could not connect to http://localhost:8545

as it says, cant find your local host.
check you IP and change your bat file to below, change to suit yours...... " 192.168.1.8" to your pc ip

shift-windows-amd64 --rpc --rpcaddr "192.168.1.8" --rpcport 6666 console

hope it helps..

pm me your mining results, it changed to wallet 4 as I found issues when your solo mining.

until a few days ago 200mh would make around 30 coins per hour.... now its half that so hoping version 4 will fix it although I am fining a few stale blocks atm....

OzDigger

newbie

Activity: 44

Merit: 0

Quote from: ?? on ??

Why am i getting when trying to mine solo on 4.0
3.0 was working fine

Quote

JSON-RPC problem. Probably couldn't connect. Retrying in 1...
miner 12:31:24|main Getting work package...
X 12:31:25|main Failed to submit hashrate.
X 12:31:25|main Dynamic exception type: class jsonrpc::JsonRpcException
std::exception::what: Exception -32003 : Client connector error: libcurl error: 7 -> Could not connect to http://localhost:8545

as it says, cant find your local host.
check you IP and change your bat file to below, change to suit yours...... " 192.168.1.8" to your pc ip

shift-windows-amd64 --rpc --rpcaddr "192.168.1.8" --rpcport 6666 console

hope it helps..

pm me your mining results, it changed to wallet 4 as I found issues when your solo mining.

until a few days ago 200mh would make around 30 coins per hour.... now its half that so hoping version 4 will fix it although I am fining a few stale blocks atm....

P-Funk

sr. member

Activity: 360

Merit: 250

Token

I'm done mining this, ocminer's suprnova pool is too big. Just checked the shift console and scrolled through too many orphaned blocks.

I see you were going to shut down the pool but changed your mind ocminer. Maybe you could just boot off the people with enough hashrate to mine solo?

P-Funk

sr. member

Activity: 360

Merit: 250

Token

Can you provide more details regarding this update? Is it a hard fork? If so, when, now? How/when will the block target change to 25 seconds happen?

hankman

full member

Activity: 182

Merit: 100

updated

ocminer

legendary

Activity: 2688

Merit: 1240

Suprnova is updated to 0.4.0

ShiftTeam

hero member

Activity: 483

Merit: 510

The Shift Team

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

dygus

legendary

Activity: 1193

Merit: 1000

Peaky Blinder

Quote from: ShiftTeam on September 23, 2015, 04:58:21 PM

Great news, thanks

ShiftTeam

hero member

Activity: 483

Merit: 510

The Shift Team

ShiftTeam

hero member

Activity: 483

Merit: 510

The Shift Team

Quote from: GoldenEye on September 23, 2015, 12:55:57 PM

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.

123sss

sr. member

Activity: 315

Merit: 250

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

spartak_t

legendary

Activity: 1960

Merit: 1176

@FAILCommunity

Quote from: dygus on September 23, 2015, 12:52:30 PM

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

It is on topic in case you are wondering.

GoldenEye

hero member

Activity: 601

Merit: 500

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

dygus

legendary

Activity: 1193

Merit: 1000

Peaky Blinder

Quote from: spartak_t on September 23, 2015, 12:43:17 PM

Quote from: defaced on September 23, 2015, 11:42:12 AM

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?

spartak_t

legendary

Activity: 1960

Merit: 1176

@FAILCommunity

Quote from: defaced on September 23, 2015, 11:42:12 AM

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.

defaced

legendary

Activity: 2198

Merit: 1014

Franko is Freedom

Quote from: ShiftTeam on September 23, 2015, 08:26:51 AM

Quote from: defaced on September 23, 2015, 07:59:43 AM

Quote from: ocminer on September 23, 2015, 05:52:55 AM

Quote from: ShiftTeam on September 23, 2015, 05:33:32 AM

Quote from: ocminer on September 23, 2015, 05:28:18 AM

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 Sad

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.

Topic: [ANN][SHIFT] The New Web | IPFS/Phantom | ShiftNrg.org Hosted Decentralized! - page 237. (Read 547597 times)