Bitcoin Forum
September 25, 2018, 04:06:06 AM *
News: ♦♦ New info! Bitcoin Core users absolutely must upgrade to previously-announced 0.16.3 [Torrent]. All Bitcoin users should temporarily trust confirmations slightly less. More info.
 
   Home   Help Search Donate Login Register  
Poll
Question: .
.
.

Pages: « 1 ... 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 224 ... 517 »
  Print  
Author Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN  (Read 712980 times)
DRPD
Legendary
*
Offline Offline

Activity: 1078
Merit: 1001


View Profile
August 12, 2016, 02:09:24 PM
 #3461

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 those peer IP's.
I will also try to do the same with my MN's to see if I can build up a stronger chain.



my controller wallet ist also in sync with http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html an moving forward fine
but i guess i receive to much staking rewards ... and a lot of my masternodes are stuck on some blocks ....
1537848366
Hero Member
*
Offline Offline

Posts: 1537848366

View Profile Personal Message (Offline)

Ignore
1537848366
Reply with quote  #2

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

Posts: 1537848366

View Profile Personal Message (Offline)

Ignore
1537848366
Reply with quote  #2

1537848366
Report to moderator
jakiman
Legendary
*
Offline Offline

Activity: 1078
Merit: 1000


jakiman is back!


View Profile
August 12, 2016, 02:16:32 PM
 #3462

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

I'm currently re-trying my first 10 MN's with only the nodes below (which I know for sure are good) & with listen=0. I'll update on how it goes shortly.

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

You can follow me on Twitter for the latest PIVX news & updates: https://twitter.com/jakimanboy
tylerderden
Copper Member
Legendary
*
Offline Offline

Activity: 1162
Merit: 1025


ICOForums.net - A Cryptocurrency & ICO Forum


View Profile
August 12, 2016, 02:35:22 PM
 #3463

What if all the masternodes are causing the fork? Especially people with bunches. What about everyone running normal wallets for a bit then slowly bringing the masternodes on after we are somewhat stable. It seems to me like we're good then someone fires up a bunch of Masternodes at once and it forks us in several directions. Worth a try I don't know, just a thought. Almost like hitting a low difficulty coin with 30 gigs of hash, it's bound to fork.


████████
██████████████
█████████████████
████████████████████
██████████████████████
████████████████████████
█████████████████████████
██████████████████████████
███████████████████████████
███████████████████████████
███████████████████████████
██████████████████████████
█████████████████████████
████████████████████████
██████████████████████
████████████████████
██████████████████
███████████████
███    ████████  
██         ████████
█         ████████

|
███
Activity Contest██████Promotion Contest██████ ̅ ̅ ̅ ̅ ̅ \
███
\___████ICO Review Contest███Signature Campaign
||
bathrobehero
Legendary
*
Offline Offline

Activity: 1554
Merit: 1026


ICO? Not even once.


View Profile
August 12, 2016, 02:46:19 PM
 #3464

I forked on the previous wallet again and was at block 230025 but getpeerinfo showed that I was connected to peers with different block heights and headers.

I don't think wallets should connect to peers that are both synced and on different heights.


With the newest wallet I'm stuck at 261107 (7fd290de5cade33ef240c77b0237f4cca6e13fbd876fb0d41f8f19b41104e3db).

RIP Bittrex
RIP Poloniex
jakiman
Legendary
*
Offline Offline

Activity: 1078
Merit: 1000


jakiman is back!


View Profile
August 12, 2016, 02:47:20 PM
 #3465

What if all the masternodes are causing the fork? Especially people with bunches. What about everyone running normal wallets for a bit then slowly bringing the masternodes on after we are somewhat stable. It seems to me like we're good then someone fires up a bunch of Masternodes at once and it forks us in several directions. Worth a try I don't know, just a thought. Almost like hitting a low difficulty coin with 30 gigs of hash, it's bound to fork.

I also agree that it's the MN's that's causing the fork.

Everyone on wrong blockhash or are stuck on block compared to MN info page should stop their wallets & MNs right now. (I did)
http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html

Going to bed now....

You can follow me on Twitter for the latest PIVX news & updates: https://twitter.com/jakimanboy
tylerderden
Copper Member
Legendary
*
Offline Offline

Activity: 1162
Merit: 1025


ICOForums.net - A Cryptocurrency & ICO Forum


View Profile
August 12, 2016, 02:53:44 PM
 #3466

What if all the masternodes are causing the fork? Especially people with bunches. What about everyone running normal wallets for a bit then slowly bringing the masternodes on after we are somewhat stable. It seems to me like we're good then someone fires up a bunch of Masternodes at once and it forks us in several directions. Worth a try I don't know, just a thought. Almost like hitting a low difficulty coin with 30 gigs of hash, it's bound to fork.

I also agree that it's the MN's that's causing the fork.

Everyone on wrong blockhash or are stuck on block compared to MN info page should stop the MNs right now. (I did)
http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html

I just figure this has never been done, trial and error, rule out every possible cause one by one and go from there, that's all we can do. It seems that whoever is hosting a bunch of Masternodes for a fee, sorry brother can't remember right now and anyone else with more than a few should bring them on slowly over time one at a time. SUCKS if that is the case, especially after that one dude made the sweet ass script but after pondering a bit, this seems like a good Avenue to pursue


████████
██████████████
█████████████████
████████████████████
██████████████████████
████████████████████████
█████████████████████████
██████████████████████████
███████████████████████████
███████████████████████████
███████████████████████████
██████████████████████████
█████████████████████████
████████████████████████
██████████████████████
████████████████████
██████████████████
███████████████
███    ████████  
██         ████████
█         ████████

|
███
Activity Contest██████Promotion Contest██████ ̅ ̅ ̅ ̅ ̅ \
███
\___████ICO Review Contest███Signature Campaign
||
jk9694
Full Member
***
Offline Offline

Activity: 278
Merit: 122


View Profile
August 12, 2016, 03:44:20 PM
 #3467

What if all the masternodes are causing the fork? Especially people with bunches. What about everyone running normal wallets for a bit then slowly bringing the masternodes on after we are somewhat stable. It seems to me like we're good then someone fires up a bunch of Masternodes at once and it forks us in several directions. Worth a try I don't know, just a thought. Almost like hitting a low difficulty coin with 30 gigs of hash, it's bound to fork.

I also agree that it's the MN's that's causing the fork.

Everyone on wrong blockhash or are stuck on block compared to MN info page should stop the MNs right now. (I did)
http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html

I just figure this has never been done, trial and error, rule out every possible cause one by one and go from there, that's all we can do. It seems that whoever is hosting a bunch of Masternodes for a fee, sorry brother can't remember right now and anyone else with more than a few should bring them on slowly over time one at a time. SUCKS if that is the case, especially after that one dude made the sweet ass script but after pondering a bit, this seems like a good Avenue to pursue

While  I host a considerable amount, they are brought on in just that manner.  The process is automated, but the nodes will only update when I tell them to.  It is a fully managed service after all.  On the same note, I am heavily involved with the developers and the testing.  Many many late nights so far.

tylerderden
Copper Member
Legendary
*
Offline Offline

Activity: 1162
Merit: 1025


ICOForums.net - A Cryptocurrency & ICO Forum


View Profile
August 12, 2016, 03:56:39 PM
 #3468

What if all the masternodes are causing the fork? Especially people with bunches. What about everyone running normal wallets for a bit then slowly bringing the masternodes on after we are somewhat stable. It seems to me like we're good then someone fires up a bunch of Masternodes at once and it forks us in several directions. Worth a try I don't know, just a thought. Almost like hitting a low difficulty coin with 30 gigs of hash, it's bound to fork.

I also agree that it's the MN's that's causing the fork.

Everyone on wrong blockhash or are stuck on block compared to MN info page should stop the MNs right now. (I did)
http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html

I just figure this has never been done, trial and error, rule out every possible cause one by one and go from there, that's all we can do. It seems that whoever is hosting a bunch of Masternodes for a fee, sorry brother can't remember right now and anyone else with more than a few should bring them on slowly over time one at a time. SUCKS if that is the case, especially after that one dude made the sweet ass script but after pondering a bit, this seems like a good Avenue to pursue

While  I host a considerable amount, they are brought on in just that manner.  The process is automated, but the nodes will only update when I tell them to.  It is a fully managed service after all.  On the same note, I am heavily involved with the developers and the testing.  Many many late nights so far.



The late nights thing sucks man, but thanks for putting in the time! I'm just spit balling, have you guys tried just getting pos going on regular wallets no masternodes? If that worked, and your system brings them on slowly maybe it's the rush of some people with you know 40 or 50 MN hitting the network all at once? Just seems like the one factor that could fork us, similar to mining pools with big hash (dedicated ahem..dick lol) hitting new coins. I could be completely wrong I'm out of the loop just been observing and thinking about cause and effect. If you guys want some help testing or just talking shit through I know my stuff so hit me up.


Edit: not sure about this either but what if pos and masternodes are pulling in different directions?  Maybe this requires 2 chains or one with alternating slots in code like line 1 pos chain line 2 masternode 3 pos 4 Mn... hell I don't know.


████████
██████████████
█████████████████
████████████████████
██████████████████████
████████████████████████
█████████████████████████
██████████████████████████
███████████████████████████
███████████████████████████
███████████████████████████
██████████████████████████
█████████████████████████
████████████████████████
██████████████████████
████████████████████
██████████████████
███████████████
███    ████████  
██         ████████
█         ████████

|
███
Activity Contest██████Promotion Contest██████ ̅ ̅ ̅ ̅ ̅ \
███
\___████ICO Review Contest███Signature Campaign
||
EcoChavCrypto
Sr. Member
****
Offline Offline

Activity: 434
Merit: 250



View Profile
August 12, 2016, 04:52:55 PM
 #3469

What if all the masternodes are causing the fork? Especially people with bunches. What about everyone running normal wallets for a bit then slowly bringing the masternodes on after we are somewhat stable. It seems to me like we're good then someone fires up a bunch of Masternodes at once and it forks us in several directions. Worth a try I don't know, just a thought. Almost like hitting a low difficulty coin with 30 gigs of hash, it's bound to fork.

I also agree that it's the MN's that's causing the fork.

Everyone on wrong blockhash or are stuck on block compared to MN info page should stop the MNs right now. (I did)
http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html

I just figure this has never been done, trial and error, rule out every possible cause one by one and go from there, that's all we can do. It seems that whoever is hosting a bunch of Masternodes for a fee, sorry brother can't remember right now and anyone else with more than a few should bring them on slowly over time one at a time. SUCKS if that is the case, especially after that one dude made the sweet ass script but after pondering a bit, this seems like a good Avenue to pursue

While  I host a considerable amount, they are brought on in just that manner.  The process is automated, but the nodes will only update when I tell them to.  It is a fully managed service after all.  On the same note, I am heavily involved with the developers and the testing.  Many many late nights so far.



The late nights thing sucks man, but thanks for putting in the time! I'm just spit balling, have you guys tried just getting pos going on regular wallets no masternodes? If that worked, and your system brings them on slowly maybe it's the rush of some people with you know 40 or 50 MN hitting the network all at once? Just seems like the one factor that could fork us, similar to mining pools with big hash (dedicated ahem..dick lol) hitting new coins. I could be completely wrong I'm out of the loop just been observing and thinking about cause and effect. If you guys want some help testing or just talking shit through I know my stuff so hit me up.


Edit: not sure about this either but what if pos and masternodes are pulling in different directions?  Maybe this requires 2 chains or one with alternating slots in code like line 1 pos chain line 2 masternode 3 pos 4 Mn... hell I don't know.

Maybe the hosting companies could rebuild nodes with the correct addnodes and include IP tables blocking the ones that are causing the fork.  There might be enough nodes between the hosting companies to stabilise the network.  Do a stealth wallet release to the hosts and their clients and make it public when there are enough stable nodes for it not to fork.  That could work right?

                ▄▄▓▓█▓▓█▀▀▀▀█▓▓██▓▄▄
             ▄▓█▓▀                ▀▓█▓█
          ▄▓█▓      ▄▄▄▓▓▓▓▓▓▄▄▄      ▀█▓▄
        ▄▓██    ▄▓▓██████████████▓▓▄    ██▓▄
       ▓██    ▓▓████████▓▀▀██████████▓    ██▓
      ▓█░   █▓█████▓▀ ▓██  ▓██ ▀▓▓█████▓    ▓▓
     ▓█    ▓█████▀  ▄▓▓██████▓▓▓▄  ▓████▓    ██
    ▓██   █████▓ ▄▓▓  ▄██░▐███▄ ▀▓▓ ░▓███▓   ██▓
    ██    █████ █▓  ▓████░▐████▓█ █▓ ░█████   ██
    ██   ▐████ ▐█  ▓█████░▐██████░ █▌ █████   ██░
    ██   ▐████ ▐██ ▓█████░▐█████▓ █▓ ░█████   ██░
    ██    ████▓ █▓█ ▀▓▓██░▐██▓▓  █▓  ▓████    ██
    ▐█▓  ░████▓▄  ▀▓▓▄▄██░▐███▄▓▓  █▓████░   ██▌
     ▐██    ▓████▓▄▄  ▀██░▐███  ▄▓▓████▓░   ██▓
      ▐█▓    █▓██████▓▓██████▓▓████████    ▐█▓
       ▐█▓▄    ▀▓██████████████████▓▀    ▄▓██
         ▐█▓▄     ▀▀▓▓████████▓▓▀▀     ▄▓██
            ▓██▄                    ▄█▓▓▀
              ▀▓█▓▓▄▄          ▄▄▓▓█▓▀
                   ▀▀▓▓██████▓▓▀▀
██
██
██
██
██
██
██
.Together we can change
❍ ❍ ❍ ❍ ❍ the internet ❍ ❍ ❍ ❍ ❍
██
██
██
██
██
██
██
  Social Media
▄███████████████████▄
██████████████████████▌
██████████████████████▌
████████████     █▀███▌
███   █████        ▐██▌
███               ▐███▌
███               ████▌
████             █████▌
█████▄▄         ██████▌
████         ▄████████▌
██████████████████████▌
██████████████████████▌
▄▓█████████████████████▓▓▄
▓██████████████████████████▌
███████████████████▓▓▀  ▓██▌
██████████████▓▀▀       ▓██▌
████████▓▀▀      ▄█    ▐███▌
███▓▀        ▄▄▓▀      ▓███▌
███▓▄▄▄   ▄▓█▓         ████▌
████████▓ ▓▌          ▓████▌
█████████▓    ▄       █████▌
██████████▌ ▄▓██▓▄   ▐█████▌
███████████████████▓▓██████▌
▐██████████████████████████
  ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
.
                  ,▄▄▄▄▄▄▄
               ▄████▀▀▀▀████▄
             ▄███`  ,▄▄,   ▀██▄
            ▐██▀  ▄███████   ██▌
          ,▄███   ████████▌  ▐██▄,
      ,▄███████▄  █▄▄██▄▄█  ▄███████▄▄
     ██████████████████████████████████,
    ▐████▌   ██████████████████   ▐█████
     ▀████▄▄████████▀  "████████▄▄████▀
       `▀████████████▄▄████████████▀▀
            '▀▀▀▀▀█████████▀▀▀▀
         ▄▄                      ▄▄
        ███          ▄▄⌐         ███
       ███           ██▌          ▀██
      ███            ██▌           ▀██
                     ██▌
tylerderden
Copper Member
Legendary
*
Offline Offline

Activity: 1162
Merit: 1025


ICOForums.net - A Cryptocurrency & ICO Forum


View Profile
August 12, 2016, 05:00:37 PM
 #3470

Sounds like an idea because yeah no matter what I do my nodes are all over the place. At one point I had them all on 2.0.3 but then stuck on a block. Everything else has resulted in nodes running 1.0.1 and 2.0.1 I'm sure that while implementing pos while having masternodes is not helping any lol. Upgrade your shit people! Or its just some dick playing games, like they do...


Right now I have 3 on 2.0.3,  2 stuck on block 261107 and  node 173.245.158.2 on block 261137 height 261653 and counting (only on the height though)

Not sure what's up

Wallet is 8 hours behind and not moving past 261107

This is using mxnsch directions exactly


████████
██████████████
█████████████████
████████████████████
██████████████████████
████████████████████████
█████████████████████████
██████████████████████████
███████████████████████████
███████████████████████████
███████████████████████████
██████████████████████████
█████████████████████████
████████████████████████
██████████████████████
████████████████████
██████████████████
███████████████
███    ████████  
██         ████████
█         ████████

|
███
Activity Contest██████Promotion Contest██████ ̅ ̅ ̅ ̅ ̅ \
███
\___████ICO Review Contest███Signature Campaign
||
muchoman
Sr. Member
****
Offline Offline

Activity: 466
Merit: 250


View Profile
August 12, 2016, 05:09:50 PM
 #3471

Sounds like an idea because yeah no matter what I do my nodes are all over the place. At one point I had them all on 2.0.3 but then stuck on a block. Everything else has resulted in nodes running 1.0.1 and 2.0.1 I'm sure that while implementing pos while having masternodes is not helping any lol. Upgrade your shit people! Or its just some dick playing games, like they do...


Right now I have 3 on 2.0.3,  2 stuck on block 261107 and  node 173.245.158.2 on block 261137 height 261653 and counting (only on the height though)

Not sure what's up

Wallet is 8 hours behind and not moving past 261107

This is using mxnsch directions exactly

This worked for me, seems to be correct chain.
getblockhash 263095
1d3ceaefc613004219292f50f5f25f3afb17bb66ea90d67fec85fde942240872

https://bitcointalk.org/index.php?topic=1262920.msg15896582#msg15896582
B1tUnl0ck3r
Sr. Member
****
Offline Offline

Activity: 602
Merit: 265


www.infowars.com/show


View Profile WWW
August 12, 2016, 05:21:34 PM
 #3472

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

I'm currently re-trying my first 10 MN's with only the nodes below (which I know for sure are good) & with listen=0. I'll update on how it goes shortly.

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

thank you for the suggestion... I tried it. However the dreaded block 261107 was insurmountable for my node. In a sense 2.0.2 was working "better"...

I read good ideas here... maybe increasing the number of trusted node for the release could be a nice option until the network stabilize. I wouldn't exclude nefarious actors trying to undermine this project...

patience... 

https://oathkeepers.org/ - https://www.defdist.org/ - https://tommyrobinson.online/ - https://laurensouthern.net/ - support assange : 36EEHh9ME3kU7AZ3rUxBCyKR5FhR3RbqVo (nicehash, even cpus) - Mike adams the health ranger http://www.healthranger.com/ -
www.infowars.com/show - https://www.jihadwatch.org/ low iqs take time to understand uncensorable systems... be it to exercise a God given rights like free speech or trade.
tylerderden
Copper Member
Legendary
*
Offline Offline

Activity: 1162
Merit: 1025


ICOForums.net - A Cryptocurrency & ICO Forum


View Profile
August 12, 2016, 05:31:44 PM
 #3473

Yep tried both of the above same result stuck on that same block. Shutting her down so if you guys fix it while I'm out I'm not dragging the network towards fork age, good luck boys.


████████
██████████████
█████████████████
████████████████████
██████████████████████
████████████████████████
█████████████████████████
██████████████████████████
███████████████████████████
███████████████████████████
███████████████████████████
██████████████████████████
█████████████████████████
████████████████████████
██████████████████████
████████████████████
██████████████████
███████████████
███    ████████  
██         ████████
█         ████████

|
███
Activity Contest██████Promotion Contest██████ ̅ ̅ ̅ ̅ ̅ \
███
\___████ICO Review Contest███Signature Campaign
||
borris123
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500


View Profile
August 12, 2016, 06:03:16 PM
 #3474

Yep tried both of the above same result stuck on that same block. Shutting her down so if you guys fix it while I'm out I'm not dragging the network towards fork age, good luck boys.

same just tried it on a few. nvm. will keep checking back till there a fix.
s3v3nh4cks
Legendary
*
Offline Offline

Activity: 1064
Merit: 1000


View Profile WWW
August 12, 2016, 08:19:51 PM
 #3475

Who has a wallet/masternode that is stuck on block 261683 I need you to send me your debug.log file please. from before that block up to getting stuck

PIVX: DPQabewFmgSFxAtZPKszNKb2E6eHqPfJt5
B1tUnl0ck3r
Sr. Member
****
Offline Offline

Activity: 602
Merit: 265


www.infowars.com/show


View Profile WWW
August 12, 2016, 08:32:17 PM
 #3476

Who has a wallet/masternode that is stuck on block 261683 I need you to send me your debug.log file please. from before that block up to getting stuck

Hello s3v3nh4cks,

Sadly I never went farther than the 261107... sorry not to be able to help you.

May the code be with you.

Courage!

https://oathkeepers.org/ - https://www.defdist.org/ - https://tommyrobinson.online/ - https://laurensouthern.net/ - support assange : 36EEHh9ME3kU7AZ3rUxBCyKR5FhR3RbqVo (nicehash, even cpus) - Mike adams the health ranger http://www.healthranger.com/ -
www.infowars.com/show - https://www.jihadwatch.org/ low iqs take time to understand uncensorable systems... be it to exercise a God given rights like free speech or trade.
werwortmann
Member
**
Offline Offline

Activity: 80
Merit: 10


View Profile
August 12, 2016, 08:37:38 PM
 #3477

Who has a wallet/masternode that is stuck on block 261683 I need you to send me your debug.log file please. from before that block up to getting stuck

I have masternode that is stuck on 261686, 3 blocks later.
Usefull?
jakiman
Legendary
*
Offline Offline

Activity: 1078
Merit: 1000


jakiman is back!


View Profile
August 12, 2016, 11:28:46 PM
 #3478

I guess the MN info page is stuck also now. While all my MN's are stopped. I just retried just 1 but still gets stuck at 261107. I'll stop for now.
I have plenty of MNs. So if the devs want me to start them up prior to next public release to build a bigger initial network, let me know. Wink

BTW, this is the script I've been using. Let me know if this isn't correct or can be improved.

Quote
#!/bin/bash
echo "Stopping darknet"
./darknet-cli stop
echo "Removing old Version"
rm darknetd
rm darknet-cli
sleep 30
echo " Removing old blockchain data "
cd
cd .darknet
rm -R blocks   chainstate  db.log        fee_estimates.dat  mncache.dat      peers.dat mnpayments.dat debug.log budget.dat backups
sed -i.bak '/listen/d' ~/.darknet/darknet.conf
echo 'listen=0' >> ~/.darknet/darknet.conf
sed -i.bak '/addnode/d' ~/.darknet/darknet.conf
echo 'connect=72.49.184.206' >> ~/.darknet/darknet.conf
echo 'connect=68.227.30.210' >> ~/.darknet/darknet.conf
echo 'connect=173.245.158.8' >> ~/.darknet/darknet.conf
echo 'connect=coin-server.com' >> ~/.darknet/darknet.conf
echo 'connect=173.245.157.244' >> ~/.darknet/darknet.conf
echo 'connect=178.254.23.111' >> ~/.darknet/darknet.conf
wget https://www.dropbox.com/s/njdjxmsvhwh6njf/.darknet.zip?dl=0
unzip .darknet.zip?dl=0 -d ~/.darknet
rm -rv .darknet.zip?dl=0
cd
echo "Downloading new version"
wget https://github.com/Darknet-Crypto/Darknet/releases/download/v2.0.3.0/darknet-cli
wget https://github.com/Darknet-Crypto/Darknet/releases/download/v2.0.3.0/darknetd
echo "setting permissions"
chmod +x darknet*
echo "Starting Darket damon"
./darknetd
sleep 120
echo "Starting Masternode"
./darknet-cli getinfo
echo "all done "

You can follow me on Twitter for the latest PIVX news & updates: https://twitter.com/jakimanboy
jakiman
Legendary
*
Offline Offline

Activity: 1078
Merit: 1000


jakiman is back!


View Profile
August 12, 2016, 11:38:15 PM
 #3479

BTW, what is causing the fork?

Will another week or two of PoW (low reward) with the new wallet before switching to PoS help?

You can follow me on Twitter for the latest PIVX news & updates: https://twitter.com/jakimanboy
NotMyFarm
Full Member
***
Offline Offline

Activity: 236
Merit: 100


View Profile
August 13, 2016, 03:18:28 AM
 #3480

Who has a wallet/masternode that is stuck on block 261683 I need you to send me your debug.log file please. from before that block up to getting stuck

Hello s3v3nh4cks,

Sadly I never went farther than the 261107... sorry not to be able to help you.

May the code be with you.

Courage!

same here
followed instructions twice
stuck on Mac Wallet 261107 and not getting anywhere

Pages: « 1 ... 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 224 ... 517 »
  Print  
 
Jump to:  

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!