Bitcoin Forum
February 16, 2019, 12:28:23 AM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
   Home   Help Search Login Register More  
Poll
Question: .
.
.

Pages: « 1 ... 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 [173] 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 ... 525 »
  Print  
Author Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN  (Read 721604 times)
BitcoinFX
Legendary
*
Offline Offline

Activity: 1764
Merit: 1069


youtu.be/O17f3lB7BFY


View Profile WWW
August 12, 2016, 09:53:01 AM
 #3441

Seeing some nodes getting stuck at:

./darknet-cli getblockhash 261107
7fd290de5cade33ef240c77b0237f4cca6e13fbd876fb0d41f8f19b41104e3db

Bitcoin without polity !?! | Get a Gapcoin slice of Mathematically constant π + new world record and attempt ongoing! | "The industry of the integrated spectacle and immaterial command owes me (us all) money." | We do not Forgive. We do not Forget. Expect Revolution Renaissance! for we are all Satoshi now? | Vision does not = Prescient | "the multiple and the multiplex!" | HODL BTC and/or buy Pizza's | Read the first chapter ... | P.S. "I Eye love found you!" 456 | Mostly harmless ... 42 | "INSERT COIN" break blocks!
1550276903
Hero Member
*
Offline Offline

Posts: 1550276903

View Profile Personal Message (Offline)

Ignore
1550276903
Reply with quote  #2

1550276903
Report to moderator
1550276903
Hero Member
*
Offline Offline

Posts: 1550276903

View Profile Personal Message (Offline)

Ignore
1550276903
Reply with quote  #2

1550276903
Report to moderator
1550276903
Hero Member
*
Offline Offline

Posts: 1550276903

View Profile Personal Message (Offline)

Ignore
1550276903
Reply with quote  #2

1550276903
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1550276903
Hero Member
*
Offline Offline

Posts: 1550276903

View Profile Personal Message (Offline)

Ignore
1550276903
Reply with quote  #2

1550276903
Report to moderator
borris123
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500


View Profile
August 12, 2016, 10:29:19 AM
 #3442

Seeing some nodes getting stuck at:

./darknet-cli getblockhash 261107
7fd290de5cade33ef240c77b0237f4cca6e13fbd876fb0d41f8f19b41104e3db


so this update hasnt worked and no point updating nodes?
Rumhurius
Legendary
*
Offline Offline

Activity: 1554
Merit: 1042


i must say no


View Profile
August 12, 2016, 10:29:26 AM
 #3443

aaaaaaaaaaaaand we have a 51%+ fork that needs another fork here.

Hardcoded good nodes, blacklisting old clients, a valid checkpoint and a forced sync from scratch should do the trick over the next update.

Patience or dump in my low orders pls.

borris123
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500


View Profile
August 12, 2016, 10:36:02 AM
 #3444

Seeing some nodes getting stuck at:

./darknet-cli getblockhash 261107
7fd290de5cade33ef240c77b0237f4cca6e13fbd876fb0d41f8f19b41104e3db


one node i have done is stuck there as well. meh!!

controller stuck there as well. followed instructions exactly.
werwortmann
Member
**
Offline Offline

Activity: 80
Merit: 10


View Profile
August 12, 2016, 10:37:13 AM
 #3445

All my nodes forked, can we get the latest blockchain to try and resync?
B1tUnl0ck3r
Sr. Member
****
Offline Offline

Activity: 658
Merit: 266


View Profile
August 12, 2016, 10:37:54 AM
 #3446

Seeing some nodes getting stuck at:

./darknet-cli getblockhash 261107
7fd290de5cade33ef240c77b0237f4cca6e13fbd876fb0d41f8f19b41104e3db


one node i have done is stuck there as well. meh!!

me too. I tried to reinstall all the wallet, with the file, multiple time, differents peers. only coin-server... what ever. impossible to get past it.  Embarrassed Cry


Seeing some nodes getting stuck at:

./darknet-cli getblockhash 261107
7fd290de5cade33ef240c77b0237f4cca6e13fbd876fb0d41f8f19b41104e3db


effectively I can confirm this... many are stuck there.

Seeing some nodes getting stuck at:

./darknet-cli getblockhash 261107
7fd290de5cade33ef240c77b0237f4cca6e13fbd876fb0d41f8f19b41104e3db


so this update hasnt worked and no point updating nodes?

yep. better no waste your time. this one isn't the update your looking for.

aaaaaaaaaaaaand we have a 51%+ fork that needs another fork here.

Hardcoded good nodes, blacklisting old clients, a valid checkpoint and a forced sync from scratch should do the trick over the next update.

Patience or dump in my low orders pls.


I don't think that hardcoding "good nodes" is the way to go. the problem we have right now is that the blockchain for most doesn't move past 261107.

Futhermore in the list given

connect=68.227.30.210
connect=173.245.157.244
connect=173.245.158.8

have been behaving badly. not on sync. and specially 68.227 was starting to sync from block 0...

It would be cool to double check the list of recommended node before publishing it...

However I strongly agree with you... patience.

btc/usd
jakiman
Legendary
*
Offline Offline

Activity: 1078
Merit: 1000


jakiman is back!


View Profile
August 12, 2016, 10:48:15 AM
 #3447

Yeah, I'm having issues also with my MNs. Back to the drawing board is needed I would say.

mikegi
Full Member
***
Offline Offline

Activity: 165
Merit: 100


View Profile
August 12, 2016, 10:58:05 AM
 #3448

Yeah, I'm having issues also with my MNs. Back to the drawing board is needed I would say.

Have you checked you masternode transactions?  Some of mine had staked to I needed to make a new address and and change the masternode.conf and the private key in the masternode's darknet.conf.

B1tUnl0ck3r
Sr. Member
****
Offline Offline

Activity: 658
Merit: 266


View Profile
August 12, 2016, 11:06:42 AM
 #3449

DEV TEAM UPDATE

Basically, new v2.0.2.0 network was going strong for first 5 hours before a bad chain got pulled in by someone and ruined it all.
So the devs are currently working to end this fiasco of forks once and for all. If you know you can help, please PM s3v3nh4cks.

As expected, all the Masternode & Stake payments post-PoS block 259200 may be rolled back to ensure it's fair to all.
We are treading on uncharted waters here as DarkNet is first crypto to have PoS on Bitcoin Core 0.10.x. So hang tight!



I just wanted to note the quality of your announcement jakiman. Very good public relation manager... I would even say crisis manager Cheesy.

Yeah, I'm having issues also with my MNs. Back to the drawing board is needed I would say.

Have you checked you masternode transactions?  Some of mine had staked to I needed to make a new address and and change the masternode.conf and the private key in the masternode's darknet.conf.



Effectively it happened to me too. Specially on wrong fork. My 0.00000001 Dnet advice would be to touch nothing and restart to sync. most of the time mine rebuild themselves because the stake is invalid.

good luck & patience.

btc/usd
q327K091
Legendary
*
Offline Offline

Activity: 1470
Merit: 1000


View Profile
August 12, 2016, 11:10:06 AM
 #3450

oh boy, switching to pos seems to have caused a shit show. As i am on the correct chain but my MN is getting mad rewards. would be a shame if the roll back killed them... good job on stopping trex deposits/withdraws

trust me mine too, it would be negative to the health of this crypto development in general to keep it, its like finding gold chain on the street that is too small fit for a neck

new upcoming awesome coin

the Gulden Coin: GKWHEPx3rQyPnbgQUSHu8gtgoRCgpqed1j
q327K091
Legendary
*
Offline Offline

Activity: 1470
Merit: 1000


View Profile
August 12, 2016, 11:12:52 AM
 #3451

DEV TEAM UPDATE

Basically, new v2.0.2.0 network was going strong for first 5 hours before a bad chain got pulled in by someone and ruined it all.
So the devs are currently working to end this fiasco of forks once and for all. If you know you can help, please PM s3v3nh4cks.

As expected, all the Masternode & Stake payments post-PoS block 259200 may be rolled back to ensure it's fair to all.
We are treading on uncharted waters here as DarkNet is first crypto to have PoS on Bitcoin Core 0.10.x. So hang tight!



cool , np at all, solid update.. suspending all master nodes even though they by a miracle  are staking, although I can't send em back to the mother ship

Yeah. Apparently the MN info page is on the wrong chain also as the devs. So it's still a mess right now.

Devs are looking at ways to ensure the next new wallet will only connect and/or download from a certain chain via hash verification.
Anyways, after the last 3 updates, last thing we want is for another round of multi-forks. So we'll just have to wait more this time. Tongue

one idea is to use testnet , test heck out of fork. premine test net with some POW (pre-fork), fork, POW again, then rollback , (dont need to be many wallets participating) then the trigger POS and probe the situation

maybe

new upcoming awesome coin

the Gulden Coin: GKWHEPx3rQyPnbgQUSHu8gtgoRCgpqed1j
B1tUnl0ck3r
Sr. Member
****
Offline Offline

Activity: 658
Merit: 266


View Profile
August 12, 2016, 11:24:01 AM
 #3452

oh boy, switching to pos seems to have caused a shit show. As i am on the correct chain but my MN is getting mad rewards. would be a shame if the roll back killed them... good job on stopping trex deposits/withdraws

trust me mine too, it would be negative to the health of this crypto development in general to keep it, its like finding gold chain on the street that is too small fit for a neck

I agree the POS is one of the major improvement of this particular coin. I hope that in the long term the situation will be stabilized. I am sure the devs are working hard on it. I see those minor inconveniences as a necessary part toward innovation.

DEV TEAM UPDATE

Basically, new v2.0.2.0 network was going strong for first 5 hours before a bad chain got pulled in by someone and ruined it all.
So the devs are currently working to end this fiasco of forks once and for all. If you know you can help, please PM s3v3nh4cks.

As expected, all the Masternode & Stake payments post-PoS block 259200 may be rolled back to ensure it's fair to all.
We are treading on uncharted waters here as DarkNet is first crypto to have PoS on Bitcoin Core 0.10.x. So hang tight!



cool , np at all, solid update.. suspending all master nodes even though they by a miracle  are staking, although I can't send em back to the mother ship

Yeah. Apparently the MN info page is on the wrong chain also as the devs. So it's still a mess right now.

Devs are looking at ways to ensure the next new wallet will only connect and/or download from a certain chain via hash verification.
Anyways, after the last 3 updates, last thing we want is for another round of multi-forks. So we'll just have to wait more this time. Tongue

one idea is to use testnet , test heck out of fork. premine test net with some POW (pre-fork), fork, POW again, then rollback , (dont need to be many wallets participating) then the trigger POS and probe the situation

maybe

I volunteer gladly a node to the test if useful for the devs. keep us informed of your needs.

btc/usd
DRPD
Legendary
*
Offline Offline

Activity: 1092
Merit: 1001


View Profile
August 12, 2016, 11:24:49 AM
 #3453

Yeah, I'm having issues also with my MNs. Back to the drawing board is needed I would say.

some of my mn's also stuck on 261107
others and windows wallet are on 261311 atm.

i guess no point in updating the rest of my nodes ....
Rageee
Newbie
*
Offline Offline

Activity: 38
Merit: 0


View Profile
August 12, 2016, 11:47:35 AM
 #3454

My wallet is still happily staking away.

getblockhash 261334

be073cebc6247bf57a59fe8a4ede62cfc06413b70e97c2cf90005fd615d98c45
boy2k
Full Member
***
Offline Offline

Activity: 166
Merit: 100


View Profile
August 12, 2016, 11:56:58 AM
 #3455

wallet is stuck like the above guys Sad
some nodes are up to date, some stuck.
sigh...
NotMyFarm
Full Member
***
Offline Offline

Activity: 236
Merit: 100


View Profile
August 12, 2016, 12:24:26 PM
 #3456

stuck wallet on
261118
+ Masternode Sync stuck too

kopykat
Newbie
*
Offline Offline

Activity: 44
Merit: 0


View Profile
August 12, 2016, 12:25:12 PM
 #3457

all nodes stuck @ block 261107.
cryptomaxsun
Hero Member
*****
Offline Offline

Activity: 1078
Merit: 540


View Profile WWW
August 12, 2016, 01:07:59 PM
 #3458

The network is still not running. purse need to update?
What happened?

jakiman
Legendary
*
Offline Offline

Activity: 1078
Merit: 1000


jakiman is back!


View Profile
August 12, 2016, 01:57:19 PM
Last edit: August 12, 2016, 02:09:29 PM by jakiman
 #3459

My main wallet is still in sync with the MN info page's block & hash which I believe is still correct.
http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html

I think a certain group of trusted members with many nodes needs to be let in first to establish a good strong network before letting everyone else jump in.
If someone is intentionally generating bad nodes to create a bad chain, hopefully that would make it much harder for the chain to split up like this.

Anyways, unless the devs voice it out beforehand, I'll provide new update from the devs as soon as I have something to post.

Here's my getpeerinfo of my main wallet. Maybe you could try connecting to only these peer IP's which definitely seem to be good.
I will also try to do the same with my MN's to see if I can build up a stronger chain.

connect=72.49.184.206
connect=68.227.30.210
connect=173.245.158.8
connect=coin-server.com
connect=104.218.120.209

Quote
23:57:51
?
getpeerinfo


23:57:51
?
[
    {
        "id" : 1,
        "addr" : "72.49.184.206",
        "addrlocal" : "60.240.49.38:59674",
        "services" : "0000000000000001",
        "lastsend" : 1471010271,
        "lastrecv" : 1471010271,
        "bytessent" : 291610,
        "bytesrecv" : 533933,
        "conntime" : 1470994048,
        "pingtime" : 0.26162600,
        "version" : 70500,
        "subver" : "/DarkNet Core:2.0.3/",
        "inbound" : false,
        "startingheight" : 261199,
        "banscore" : 0,
        "synced_headers" : 261466,
        "synced_blocks" : 261466,
        "inflight" : [
        ],
        "whitelisted" : false
    },
    {
        "id" : 2,
        "addr" : "68.227.30.210",
        "addrlocal" : "60.240.49.38:59676",
        "services" : "0000000000000001",
        "lastsend" : 1471010271,
        "lastrecv" : 1471010271,
        "bytessent" : 14662698,
        "bytesrecv" : 1738611,
        "conntime" : 1470994054,
        "pingtime" : 17.42019800,
        "version" : 70500,
        "subver" : "/DarkNet Core:2.0.3/",
        "inbound" : false,
        "startingheight" : 145635,
        "banscore" : 0,
        "synced_headers" : 147393,
        "synced_blocks" : -1,
        "inflight" : [
        ],
        "whitelisted" : false
    },
    {
        "id" : 4,
        "addr" : "173.245.158.8",
        "addrlocal" : "60.240.49.38:59690",
        "services" : "0000000000000001",
        "lastsend" : 1471010271,
        "lastrecv" : 1471010271,
        "bytessent" : 375459,
        "bytesrecv" : 562009,
        "conntime" : 1470994069,
        "pingtime" : 0.25908700,
        "version" : 70500,
        "subver" : "/DarkNet Core:2.0.3/",
        "inbound" : false,
        "startingheight" : 261200,
        "banscore" : 0,
        "synced_headers" : 261466,
        "synced_blocks" : 261466,
        "inflight" : [
        ],
        "whitelisted" : false
    },
    {
        "id" : 5,
        "addr" : "coin-server.com",
        "addrlocal" : "60.240.49.38:59693",
        "services" : "0000000000000001",
        "lastsend" : 1471010271,
        "lastrecv" : 1471010271,
        "bytessent" : 284962,
        "bytesrecv" : 537113,
        "conntime" : 1470994075,
        "pingtime" : 0.25945500,
        "version" : 70500,
        "subver" : "/DarkNet Core:2.0.3/",
        "inbound" : false,
        "startingheight" : 261200,
        "banscore" : 0,
        "synced_headers" : 261466,
        "synced_blocks" : 261466,
        "inflight" : [
        ],
        "whitelisted" : false
    },
    {
        "id" : 134,
        "addr" : "104.218.120.209",
        "addrlocal" : "60.240.49.38:61621",
        "services" : "0000000000000001",
        "lastsend" : 1471010271,
        "lastrecv" : 1471010271,
        "bytessent" : 233146,
        "bytesrecv" : 432073,
        "conntime" : 1470999944,
        "pingtime" : 0.31801500,
        "version" : 70500,
        "subver" : "/DarkNet Core:2.0.3/",
        "inbound" : false,
        "startingheight" : 261289,
        "banscore" : 0,
        "synced_headers" : 261466,
        "synced_blocks" : 261466,
        "inflight" : [
        ],
        "whitelisted" : false
    }
]

mxnsch
Sr. Member
****
Offline Offline

Activity: 462
Merit: 250


Miner, Firmware Tinkerer, Whisky Drinker


View Profile
August 12, 2016, 02:08:50 PM
 #3460

You need to follow the instructions carefully guys. All my masternodes and wallet are at 261474 and the status page is current, too.

This is what i did:

Wallet owners:
* stop the wallet
* delete all files except the darknet config, masternode config and wallet.dat (+backups)
* remove all addnode and connect instructions, except those (the following nodes worked reliable for me):
Code:
connect=72.49.184.206
connect=74.118.192.18
connect=138.68.50.249
connect=173.245.157.244
connect=173.245.158.8
connect=coin-server.com
connect=24.119.187.242
connect=178.254.23.111
* put the current chainfiles from dropbox in your data folder
* start the 2.0.3 wallet
* unlock the wallet

Masternodes owners:
* stop all nodes
* update the darknetd binary to 2.0.3
* delete all files except the darknet config containing your masternode private key
* put the current chainfiles from dropbox in your data folder
* start all nodes, one by one

I also drop all packages by specific masternodes that were especially unreliable in the past with
Code:
iptables -A INPUT -s 68.227.30.210 -j DROP
iptables -A INPUT -s 173.245.157.244 -j DROP
iptables -A INPUT -s 173.245.158.8 -j DROP

██  ███  masternode ninja ██  ███
Pages: « 1 ... 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 [173] 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 ... 525 »
  Print  
 
Jump to:  

Bitcointalk.org is not available or authorized for sale. Do not believe any fake listings.
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!