|
can't get the rpc port to show no matter what i try, i wonder if this particular wallet-builder source has been created off an old fork of bbqcoin - where submitblock etc isn't actually implemented..
this has been amusing from beginning to end - now the exchange rocks up saying no source? solomineguy - just leave, honestly.. walk away - for one btc? you're a joke.
|
|
|
|
|
anyway, 10 days later... no nodes?
no block source available..
|
|
|
|
Such a shame! Seemed like a good idea at the time...  While some people want to make real great things someone want only hurt others. I have to admit that the idea behind this coin could work but after the launch the difficulty to mine increased so bad that the idea about mining solo couldn't work anymore. 5minutes of work: setup your p2pool, rent hashpower needed, hit the power into your pool that is called solo. no it isnt. solo-mining means you point your mining program directly at the rpc port of the wallet. a p2pool is the worst example to use for pool mining. running a p2pool means it reformats the chain so everytime anyone finds a block, the reward gets evenly split amongst all that are participating. what you probably meant is, getting a block splitter like stratum-mining (or the mpos dropin replacement from nomp), setting it up against a wallet, then renting hashpower to mine against it yourself - this still isnt solo-mining, its pool mining with one user. |
|
|
|
|
dev,
altcoincalendar and the clock you have on this page have two different countdowns.
is the coin launching in < 4 hours or still 1 day 4 hours to go?
its nearly 10pm on the 5/08 here..
james
|
|
|
|
{
"version" : "nvc-v1.1.2.build-g32a928e-bdb-gcc",
"protocolversion" : 70019,
"walletversion" : 60000,
"balance" : x,
"unspendable" : 0.00000000,
"newmint" : 9.00000000,
"stake" : 0.00000000,
"blocks" : 20991,
"timeoffset" : 0,
"moneysupply" : 1258153.89093600,
"connections" : 1,
"proxy" : "",
"ip" : "x.x.x.x",
"difficulty" : {
"proof-of-work" : 0.00025390,
"proof-of-stake" : 0.03124954
},
"testnet" : false,
"keypoololdest" : 1434032778,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"mininput" : 0.00010000,
"errors" : ""
}
I wonder though what happens when more nodes come online regarding longest chain. I'll keep my miners idling before more nodes are online and have agreed for a chain.
There may temporarily be two versions of the chain as people still have their 70018 nodes running - essentially it boils down to version of the wallet that initial addnode/exchange runs. Once enough 70019 hosts are online (which only talk to versions => 70019), the old chain will no longer be accepted. |
|
|
|
I think it says so much about the dev, as he has gone through many troubles and has not given up. I certainly will be investing in this coin with such a good dev with a "no quit attitude!!!" AWESOME!! When new wallet is fixed Ill post on my website and endorse it. I get around 20,000 hits a week. All crypto enthustiasts. www.bitcoinlasvegas.netVegas I just really respect that after all the problems that he has endured with this coin not only did he "NOT QUIT" but he had no shame whatsoever telling the community that he was unable to fix the problem and reached out for the help to have it fixed properly and also never once asked the community to pay for any of the expenses that he may have incurred on this project  That says a lot right there to me that this guy honestly cares about his community and doesn't think that lying to them about things is the way to go about it One of the only reasons I got into EOC in the first place  Cheers seems to be one of the best unexpected features of cryptocurrency; half the time its not even about the coins/worth, its about the journey and being involved.. just having your own currency is reason enough for some - dev now has url's/code - i will hang about for a bit just in case.. |
|
|
|
|
Appears we have a comedian in here:
{
"addr" : "24.7.144.109:8737",
"services" : "00000001",
"lastsend" : 1438111978,
"lastrecv" : 1438111978,
"bytessent" : 223,
"bytesrecv" : 323,
"conntime" : 1438111976,
"version" : 70018,
"subver" : "/Satoshi:1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 20987,
"banscore" : 0
},
Everyone, feel free to packet this IP - hasn't updated the version number that matters regardless..
|
|
|
|
ok, win client syncs past block 20987.. going to nudge the version to 70019, also set the caddr_time_version so this wallet becomes a mandatory fork, recompile, send to dev.. lets hope this time it compiles bit quicker |
|
|
|
@kevin1234a: Ty for your appreciation, glad I could help. I do not need any bounty, I was just curious and am still learning the ins and outs of blockchain tech.
That said, I believe just getting the chain to move is ev. not sufficient, I suspect since everybody mined a few blocks on his own chain, we are now all on a different fork. The one mining away the most of these cheap blocks will probably win the race for longest chain (Fork-Fest anyone?).
Also regarding muddafudda's fix: As I suspect the problem arose because a block with invalid time (in the future) was accepted by the chain and resulted in a negative target spacing I could imagine it would be better to trigger the fix not from time but from a block number.
And I would also like to ask the experts around if it wouldn't make sense to bump the clients version number if that hasn't been done already?
Hopefully somebody with more insight could comment on my above points.
Happy to see some movement again with EOC, I like the coins specs.
Once i've confirmed that the wallet syncs past 20987 altogether, i'll bump the version, send changes to dev.. i forgot to change the initial addnode when launching test, so resyncing again.. |
|
|
|
 testing.. |
|
|
|
|
We'll see - wrestling with compile errors, standard fare QT stuff
|
|
|
|
|
No problem - WinQT/64 wallet is 15 minutes away, just compiling libraries
|
|
|
|
Confirm pls
version" : "nvc-v1.1.1.build-g32a928e-bdb-gcc",
"protocolversion" : 70018,
"walletversion" : 60000,
"balance" : 0.00000000,
"unspendable" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 21057,
"timeoffset" : 0,
"moneysupply" : 1258219.89093600,
"connections" : 1,
"proxy" : "",
"ip" : "192.52.166.80",
"difficulty" : {
"proof-of-work" : 0.00263536,
"proof-of-stake" : 0.03124954
},
"testnet" : false,
"keypoololdest" : 1438068987,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"mininput" : 0.00010000,
"errors" : ""
root@chainserv:/usr/coin/EiniaOraNewSourceCode/src# ./EiniaOraCoind -daemon -rpcuser=x -rpcpassword=x -rpcallowip=10.0.1.* -rpcport=8736 -datadir=datadir getmininginfo { "blocks" : 21057, "currentblocksize" : 1000, "currentblocktx" : 0, "difficulty" : { "proof-of-work" : 0.00263536, "proof-of-stake" : 0.03124954, "search-interval" : 0 }, "blockvalue" : 1000000, "netmhashps" : 0.00117585, "netstakeweight" : 715099.32003838, "errors" : "", "pooledtx" : 0, "stakeinputs" : 0, "stakeinterest" : 3650000, "testnet" : false } |
|
|
|
|
Just PM'd dev to see if its ok for me to compile and release on here (ie. not cutting his grass).
However, i've no issues quickly typing up step by step compile instructions for Debian 8.1 x64.
(I can already hear the smart ones downloading the Debian ISO right now..)
|
|
|
|
Can someone compile windows wallet with the fix if the Dev hasn't done that already? That would be sweet and I would be downloading it for sure Cheers bounty? I'll pay you for a newly compiled windows wallet with the fix Whatcha want? let me confirm that this resolves the issue 100%, have already been trashed on this very same thread once already.. am receiving more than a few orphaned blocks, but this could very well just be my equipment  |
|
|
|
Can someone compile windows wallet with the fix if the Dev hasn't done that already? That would be sweet and I would be downloading it for sure Cheers bounty? |
|
|
|
just a headsup bud, rpc is 4474 also - the one miner you do have on the pool is mining garbage.. (diff isnt 1) |
|
|
|
Can't connect to it. I am trying with: cpuminer-multi-x64 -a scrypt -q -t 4 -o stratum+tcp://darkeye.slugmonkeypool.net:3336 -u xxxxxx -p xxxxx Error message: [2015-07-20 22:53:38] ...retry after 10 seconds [2015-07-20 22:53:50] Stratum connection failed: Failed to connect to darkeye.slugmonkeypool.net port 3336: Connection r efused Any idea why? probably this: Unable to connect to wallet RPC service: RPC call failed: Failed to connect to localhost port 19334: Connection refused |
|
|
|
|
Show Posts
