This morning I was sure to be able to post a message here about how it was working great, since my last post it was smooth sailing. Sadly now I am like you blocked at this block:
getblockhash 263844
8c0ffc3fd677bc2b30bdc8d56b6bb3cd39605a56c617e66aebf8fa2c64b33dd3
Do we have the same?
Confirmed. It's not a fork - just not staking any more. darknet-cli getblockhash 263844 8c0ffc3fd677bc2b30bdc8d56b6bb3cd39605a56c617e66aebf8fa2c64b33dd3 |
|
|
|
Is everything fixed now with wallets forks and chains? I want to buy some more and transfer them to my wallet but need to be sure all is working fine.
Looks like bittrex is up, I guess sending a small amount first and seeing that it works. I would be hesistant to use Yobit, especially if you want to get the coins out soon. |
|
|
|
|
darknet-cli getblockhash 261100
faa767e489cb29df8184f423c36610ff9c78fbb8d360792d6d5f0d45c46d7a52
On all nodes and wallet.
|
|
|
|
|
Moving again... :-/
Stuck:
darknet-cli getblockhash 260724
3289922ce601205fb0b9cf7aef5d3e7a7ce2e827fbd357dc19813510fa2052a
Not Stuck:
darknet-cli getblockhash 260724
6d5e6188e26fae2d44149a6b4d0e972975d2bf60c533b505553eb8058db3163c
darknet-cli getblockhash 260742
aa74039ff31212a746298450c3c7ab670528757e987093c906a191b536010f2
|
|
|
|
defo stuck at 260709
Me too. All at 260709.  |
|
|
|
|
Ok...
A couple of my masternodes stuck at 260598,
Restarted and they are ok... "status" : "Masternode successfully started" without having to do anything on the controller. After restarting, the blockhash for 260598 changed to the hopefully correct one.
NOT stuck:
darknet-cli getblockhash 260598
246a20ed8ceb48a6d7975a69993db5e4edee95470d9480e0f95673785e12a5e5
STUCK:
$ darknet-cli getblockhash 260598
d0e84fd138bb89b3a8881dadd4f50baf78f992361e7715ea611235c41a6cdda0
darknet-cli getchaintips
[
{
"height" : 260709,
"hash" : "a070dc031723cda052a3f4798c456324d6c9badddb1acb02525750697d46563d",
"branchlen" : 0,
"status" : "active"
},
{
"height" : 260598,
"hash" : "d0e84fd138bb89b3a8881dadd4f50baf78f992361e7715ea611235c41a6cdda0",
"branchlen" : 19,
"status" : "valid-headers"
},
{
"height" : 260595,
"hash" : "b33099e3006b92b48c60e7ca6e31eb04b2405733645245e67c6bf15e8649c0ba",
"branchlen" : 1,
"status" : "valid-fork"
},
{
"height" : 259901,
"hash" : "2a83196b23e76314d50d8cdd11bb370db28a686dda852c3f9b9c9305e640255d",
"branchlen" : 14,
"status" : "valid-fork"
},
{
"height" : 259817,
"hash" : "80649f7287034ff01382de577e2e4367a8dfde83b0e72d765e75a3183dc87b06",
"branchlen" : 17,
"status" : "valid-fork"
},
{
"height" : 259814,
"hash" : "8602ff8f646378dfcfba163f8b428f82ddb5a42962d4b54270b323dca02f41a1",
"branchlen" : 14,
"status" : "headers-only"
}
]
|
|
|
|
Looks like it works for me, all masternodes up, wallet reporting Staking Active. If you are getting "stuck", check how many peers you have and check the end of the logfile. If you are crashing, check the logs, maybe a corrupt wallet file. For me, using a backup from before PoS helped. For masternodes, it's possible that wallet.dat even if it is empty could cause a problem too. For those who posted blocks earlier... here is what I see... $ darknet-cli getblockhash 259539
29faf736f01c608e206b853b10cf3fde2e3909a306f4fbc39123d4300349dd0a
$ darknet-cli getblockhash 259804
59b69b7ceaee9ebd668b7a873509d7b4425659437740d4426bfa7ad92339709c
$ darknet-cli getblockhash 260048
ac1be0a29bab70204ef81f11c29ab14952414ec840e8e36d6f3cf3df8f87a454
darknet-cli getblockhash 260140
$481e390a121c66fbe587f7c6acd5eb85db92480206bfc55d02ad2f35bc8c2558
darknet-cli getblockhash 260150
c36be63959cdb6194bc55149d11f1b32ae0655cd20ef27866550145765ac2e93
$ darknet-cli getblockhash 260176
37680d1fd0189f2b0f0044f70f74176270826182a08d3b810fb39cc2b04d8ab9
darknet-cli getblockhash 260224
33bf1fc91a1214044c64ecb980247f609bf5911a1d4013c60f81471ec794b780
All masternodes are "status" : "ENABLED" from the wallet, and "status" : "Masternode successfully started" on the masternode. It would be nice if the category field when running listtransactions from darknet-cli was more clear... (instead of just send and recieve) I guess my masternodes are approving blocks... transactions are all pretty close to 38.25 DNET. Any ideas of what kind of balances are needed to stake at the moment? If you are using the Linux darknet-cli ... here is a oneliner make limit the output of listtransactions to more relevant information. Maybe someone would like to figure out add a comment that will put a dashed line between blocks or make a perl script. :-) darknet-cli listtransactions "*" 1000 | grep -e account -e address -e category -e amount -e confirmations -e fee |grep -v -e txid -e bcconfirmations | sed 's/\(.*account.*\)/\n\1/' Output looks like this... (with some additions sed to remove addresses... "account" : "asdfg",
"category" : "send",
"amount" : 0.00000000,
"fee" : 44.99998960,
"confirmations" : 703,
"account" : "",
"address" : HIDDEN
"category" : "send",
"amount" : -38.25000884,
"fee" : 44.99998960,
"confirmations" : -1,
"account" : "",
"address" : HIDDEN
"category" : "send",
"amount" : -29.24998076,
"fee" : 44.99998960,
"confirmations" : -1,
"account" : "",
"category" : "send",
"amount" : 0.00000000,
"fee" : 44.99998960,
"confirmations" : -1,
"account" : "qwerty",
"address" : HIDDEN
"category" : "receive",
"amount" : 38.25000884,
"confirmations" : 312, Also, it's nice to see lots of TOR nodes. At the moment, the masternode distrubution is: Total: 204 TOR: 133 IPv6: 35 IPv4: 36 I agree with borris123 that fixing things belongs in a testnet, probably more could have been done there initially, understand that not all problems, behaviour, misbehaviour can be simulated in a test network. So, is this another practice? Are there any more problems with the blockchain? Does Staking work? Are the remaining problems, having to do with improper configuration. Are we stable enough? Is this fair enough to for us to move on? |
|
|
|
INTERIM UPDATE AUG 17 | INCREASING BLOCK REAWRD
Today has been a very busy day as we have been working tirelessly to find out what caused the
anomalies seen on our blockchain that prompted Bittrex to intervene and shut down our market.
What happened?
About 16 hours ago, we received a message from Bittrex informing us that they had seen some
suspicious transactions that tripped their security and disabled the wallets and suspended trading.
We corresponded with Richie and quickly found out that we have fallen victim to what appeared
to be a double spend / mining attack where a user was able to send coins to Bittrex, sell them
and then have them reappear in his wallet. A brief investigation revealed a huge hashrate spike
on our network which confirmed this theory.
Quickly after all this, amidst all the confusion, we have been contacted by the person who was
responsible, stating he was one of a group of developers working on a closed project that mined
a private testchain for SHIFT which got accidentally released to the public.
It's really great to see that Bittrex has security measures like this in place. It shows that the are really on the ball and makes me that much more comfortable using them. Great to see that there has been communication between all parties involved, and that things have been worked out. Any news about when Bittrex will enable the wallet and trading? In other news, I have been very occupied with non-crypto activities the past couple months. I have a bit more free time now and able to spend some of this time with SHIFT. |
|
|
|
hi. i have 240 mh. But i want to mine solo, and dont know how to do it =) Can you plz connect with me ( pestario@bk.ru), who have free time and good mood =)) I do not understand what i need download, how registr and what and how to run mining. I know nothing. Only exp pool mining Ξthereum. My bad english, sry. Thank you  I'd suggest checking ExEric3's post and trying that first. https://bitcointalk.org/index.php?topic=1155284.msg15608268#msg15608268If you have trouble syncing the blockchain, try a Shift 3.0.1 binary, to sync and then upgrade to 3.1.0. I had trouble syncing the chain with the 3.1.0 from scratch, (compiled from github). |
|
|
|
Devs are scammers and can't make anything good! Dump your coins now!!!!!11  Sorry, just wanted to make this thread looking like any other thread on this forum. I think devs are doing good work and the community is great. Updating my wallet now. Sadly there is a big problem with the devs of this coin. They believe to be so great that they don't answer most questions of the new comers here. Sadly as proved, their arrogance is only as high as their coding is weak. Why after all the positive messages I wrote about this coin I say such words? I asked repeatedly for a linux 32bit version... being ignored by them, I decided to compile myself. So after learning all the basis of the process, which is by the way super user unfriendly (like everything on linux: this unnecessary complication is just used to mask the lack of coding power and smartness to make it user friendly) but easy. I see that one the ./configure needs to be modified with .ac at the end and worst of all the make command doesn't work for a yet unknown reason to me. So to resume, their arrogant and unhelpful attitude, like if they invented the wheel, is detrimental to the community and eventual growth of this coin. I find it sad. If you are building from git, you need to generate the configure file. ( the .ac means that "autoconf" uses this to generate the file). The autogen.sh script calls autoreconf which calls autoconf among other things. git pull ./autogen.sh ./configure make It is mentioned in the "INSTALL" file in the root of the repository. I haven't tried compiling it for 32 bit Linux. I would suppose it would be ok if the dependencies are met. |
|
|
|
|
A question about the masternodes.
Do they need to be started by the controller wallet or will their status change when blocks start being staked?
I can't remember exactly what the masternode statuses I saw yesterday before starting were but, it don't they activated until after I started them.
Anyway, I won't loose sleep tonight. Will leave a terminal sleeping and ready to start them.
|
|
|
|
|
80 masternodes up a few minutes ago, now 143, now 163, now 188... now 220 ... 17 nodes on tor.
Past bedtime... Thanks! Good night.
|
|
|
|
|
"Not capable masternode: Hot node, waiting for remote activation"
... here goes...
|
|
|
|
|
$ darknet-cli getblockhash 259200
0000000000b469fb33c2e0911409d6c06183c13e6dd88ac5d827d39ecf3e1b4a
$ darknet-cli getblockhash 259201
fc21adc0a966464eecee91fb0eb785623b041befd67a2b5f433f1d8f750e2a6c
.... is this early?
"id" : 2,
"addr" : "72.49.184.206:51472",
"addrlocal" : "197.231.221.211:21027", (TOR)
"services" : "0000000000000001",
"lastsend" : 1471394897,
"lastrecv" : 1471394898,
"bytessent" : 1959,
"bytesrecv" : 10789,
"conntime" : 1471393576,
"pingtime" : 0.89766800,
"version" : 70650,
"subver" : "/DarkNet Core:2.1.0/",
"inbound" : false,
"startingheight" : 259201,
"banscore" : 0,
"synced_headers" : -1,
"synced_blocks" : -1,
"inflight" : [
],
"whitelisted" : false
"id" : 16,
"addr" : "173.245.158.8:51472",
"addrlocal" : "197.231.221.211:2565", (TOR)
"services" : "0000000000000001",
"lastsend" : 1471394896,
"lastrecv" : 1471394896,
"bytessent" : 626,
"bytesrecv" : 9809,
"conntime" : 1471394175,
"pingtime" : 0.24584900,
"version" : 70650,
"subver" : "/DarkNet Core:2.1.0/",
"inbound" : false,
"startingheight" : 259201,
"banscore" : 0,
"synced_headers" : -1,
"synced_blocks" : -1,
"inflight" : [
],
"whitelisted" : false
"id" : 29,
"addr" : "173.245.158.8:51472",
"addrlocal" : "176.126.252.12:61328", (TOR)
"services" : "0000000000000001",
"lastsend" : 1471394808,
"lastrecv" : 1471394809,
"bytessent" : 690,
"bytesrecv" : 9928,
"conntime" : 1471393967,
"pingtime" : 0.94120200,
"version" : 70650,
"subver" : "/DarkNet Core:2.1.0/",
"inbound" : false,
"startingheight" : 259201,
"banscore" : 0,
"synced_headers" : -1,
"synced_blocks" : -1,
"inflight" : [
],
"whitelisted" : false
|
|
|
|
just an hour left. hope it all goes smoothly.
oooo hero member now lol
Congrats! I lost the "Jr. Member" status recently. |
|
|
|
Now running version v2.0.5.0-3bddcd3. Wallet only. Any way that block reorganization requests can be used to exploit the network by a malicious staker or masternode? For example to fork the chain? $ darknet-cli getblockhash 263033 6cc1893f9f06f29157f23595f3f2d812a47fbf263ee23af7457d1c5d5d05e012 $ TZ=UTC date Mon Aug 15 22:53:21 UTC 2016 |
|
|
|
a little check to see if everyone is on the same chain... I got stuck at 262851. relaunched the wallet and it synced again and move perfectly to the next blocks...
getblockhash 262860
b5e4fdf0bf92076f1749179f0e5d11fdbb79a2777adc53a5f6b7e62278d89fbb
$ darknet-cli getblockhash 262860 b5e4fdf0bf92076f1749179f0e5d11fdbb79a2777adc53a5f6b7e62278d89fbb darknet-cli getchaintips [ { "height" : 262868, "hash" : "d7d87bbbaaf7d32df05b21595ec080de7e13e402bb84a686913a13d0b02682f6", "branchlen" : 0, "status" : "active" }, { "height" : 262677, "hash" : "33f4ac34855efd8ffcc376999723a5e65c30e615e232be18c96925ec5001c763", "branchlen" : 3, "status" : "valid-headers" }, { "height" : 262545, "hash" : "403ea002e727e8050b191b0a64c0ceded6e61c10e225cbee5893dad3b1d6c026", "branchlen" : 18, "status" : "valid-fork" }, { "height" : 262496, "hash" : "1d24a317d4eba89ed358b122b3f39c47fead6422af7753244e03514f0c3ee85b", "branchlen" : 1, "status" : "valid-fork" }, { "height" : 262445, "hash" : "e9cf640b337db2572406860cecb1fce771f8030cd85d7ac848acccb3a5079e06", "branchlen" : 3, "status" : "valid-fork" $ TZ=UTC date Mon Aug 15 20:21:46 UTC 2016 |
|
|
|
Windows wallet 2.0.5.0 crashes randomly, 10 times already and masternode will not start also.
Previous version did not have such problems.
masternode start
Not capable masternode: Could not find suitable coins!
masternode status
{
"vin" : "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
"service" : "127.0.0.1:51472",
"status" : "Not capable masternode: Could not find suitable coins!"
}
Maybe Your coins from your masternode tx have staked? Then the tx is now spent. |
|
|
|
|
Cool!
But unfortunately, busy for the next several hours... Good luck!
|
|
|
|
|
Show Posts
