Author

Topic: |ANN| DAS - Decentralized and Secure. Private Send. Masternodes. - page 103. (Read 153983 times)

newbie
Activity: 28
Merit: 0
Hey guys - if you are having trouble syncing/confirming/not accepting blocks, you need to ban peers in your peer list that are using version 12.1. In your wallet, go to Tools>Peers list. Right click any node using 12.1 and ban for however long you see fit. I chose 24 hours to give people a chance to update, but will continue to check and ban as necessary. This fixed ALL of my problems.

Fixed my issue! Wallet synced after banning all 12.1 clients

Please update to 12.2 people!

Please post your output of getpeerinfo and getblocktemplate
member
Activity: 73
Merit: 10
Hey guys - if you are having trouble syncing/confirming/not accepting blocks, you need to ban peers in your peer list that are using version 12.1. In your wallet, go to Tools>Peers list. Right click any node using 12.1 and ban for however long you see fit. I chose 24 hours to give people a chance to update, but will continue to check and ban as necessary. This fixed ALL of my problems.

Fixed my issue! Wallet synced after banning all 12.1 clients

Please update to 12.2 people!
newbie
Activity: 28
Merit: 0
Hey guys - if you are having trouble syncing/confirming/not accepting blocks, you need to ban peers in your peer list that are using version 12.1. In your wallet, go to Tools>Peers list. Right click any node using 12.1 and ban for however long you see fit. I chose 24 hours to give people a chance to update, but will continue to check and ban as necessary. This fixed ALL of my problems.

Banned all peers. Still not fixed - there is for sure still a issue!

Please post your output of getpeerinfo and getblocktemplate
newbie
Activity: 56
Merit: 0
Hey guys - if you are having trouble syncing/confirming/not accepting blocks, you need to ban peers in your peer list that are using version 12.1. In your wallet, go to Tools>Peers list. Right click any node using 12.1 and ban for however long you see fit. I chose 24 hours to give people a chance to update, but will continue to check and ban as necessary. This fixed ALL of my problems.
newbie
Activity: 3
Merit: 0
My transactions aren't confirming with the new wallet.

i have 33 confirmations in a little over 30 minutes. I've sent and received a few transactions, no problems. The new update works great!

Nice work dev!!
hero member
Activity: 525
Merit: 500
My transactions aren't confirming with the new wallet.
sr. member
Activity: 475
Merit: 250
important : all users need to update to the version 12.2

Thanks
full member
Activity: 231
Merit: 100
full member
Activity: 331
Merit: 105
What logo did we decided on ? I really like the red one.

I also like the red one. Looks really cool. But the final decision is for the dev.
newbie
Activity: 28
Merit: 0
Dear all!
How to i can setup my marternode in my wallet! I try this help but i can not run it

Some pages back dev describbed it.

Can you please post your getblocktemplate and your getpeerinfo if any of your 12.2 nodes are in sync?
hero member
Activity: 938
Merit: 517
Dear all!
How to i can setup my marternode in my wallet! I try this help but i can not run it

Some pages back dev describbed it.
sr. member
Activity: 299
Merit: 250
Dear all!
How to i can setup my marternode in my wallet! I try this help but i can not run it
newbie
Activity: 28
Merit: 0
I hope the developer wouldn't abandon this again just like what he did to the last coin. I hope this is not Part 2 of it. Sad

I think not because everything working fine. Just some stupids here who are on the wrong chain crying like babys.
For me everything is fine and my Masternodes get paid.

I might give it a try once the Mac wallets are released but you can't blame people for having complaints about a masternodes performance they are suppose to be solid income and kinda hard when they either crash or get on the wrong chain. Hopefully the dev can polish the performance with the next releases after they get some rest.


Ah. I see.  How do you solve?

Ah. I see. How do you solve?

The problem is the most are here really noobs. They need a tutorial for everythink. If you now how mn work and you are able to use a console than you have 0 problems here
OMG, Finally. we have an expert here. Please SIR answer my question.
I rent some hash and point it to the pool in the OP (hexpool). After hours and hours of mining (I have paid for) mr. hexpool says "hey, we are on the fork".
Mr expert, in your humble opinion, have I being fucked by hexpool?

The problem is the hexpool owner. he dont know what he is doing
And here we get to the conclusion, a lot of people (including you) know what they are doing ARE YOU HEXPOOL OWNER?
Welcome to the bitcoin world guys, meat mincer of virtual wealth.

If you've read the thread you would have noticed that we are very active in this thread. This is no scam, updating to the latest wallet just made all immature blocks orphaned (as they didn't include MN payments).

So nevertheless, chain will NOT sync from any of the 12.2 nodes - ALL 12.2 nodes report height/synced_blocks status -1 - which means they all are thinking they are still downloading blocks.


I agree.




How do you solve?

I did not solve. In my opinion there is no working chain on 12.2

And why it worked for use? my mn running great

You can see that every 12.2 node does not report synched blocks! Look at your output from getpeerinfo



You can also see in the debug log that there are many 12.2 nodes which stopped syncing:

2017-07-26 12:14:25 receive version message: /Das Core:0.12.2/: version 70201, blocks=16824, us=185.137.97.24:57210, peer=6, peeraddr=35.184.44.214:9399
2017-07-26 12:14:26 receive version message: /Das Core:0.12.2/: version 70201, blocks=16480, us=185.137.97.24:56618, peer=7, peeraddr=46.101.136.245:9399
hero member
Activity: 938
Merit: 517
I hope the developer wouldn't abandon this again just like what he did to the last coin. I hope this is not Part 2 of it. Sad

I think not because everything working fine. Just some stupids here who are on the wrong chain crying like babys.
For me everything is fine and my Masternodes get paid.

I might give it a try once the Mac wallets are released but you can't blame people for having complaints about a masternodes performance they are suppose to be solid income and kinda hard when they either crash or get on the wrong chain. Hopefully the dev can polish the performance with the next releases after they get some rest.


Ah. I see.  How do you solve?

Ah. I see. How do you solve?

The problem is the most are here really noobs. They need a tutorial for everythink. If you now how mn work and you are able to use a console than you have 0 problems here
OMG, Finally. we have an expert here. Please SIR answer my question.
I rent some hash and point it to the pool in the OP (hexpool). After hours and hours of mining (I have paid for) mr. hexpool says "hey, we are on the fork".
Mr expert, in your humble opinion, have I being fucked by hexpool?

The problem is the hexpool owner. he dont know what he is doing
And here we get to the conclusion, a lot of people (including you) know what they are doing ARE YOU HEXPOOL OWNER?
Welcome to the bitcoin world guys, meat mincer of virtual wealth.

If you've read the thread you would have noticed that we are very active in this thread. This is no scam, updating to the latest wallet just made all immature blocks orphaned (as they didn't include MN payments).

So nevertheless, chain will NOT sync from any of the 12.2 nodes - ALL 12.2 nodes report height/synced_blocks status -1 - which means they all are thinking they are still downloading blocks.


I agree.




How do you solve?

I did not solve. In my opinion there is no working chain on 12.2

And why it worked for use? my mn running great
legendary
Activity: 1078
Merit: 1042
www.explorerz.top
If you updated on 12.2 and you still have issues:

(unix)

- backup your wallet (if any coins in)
- download the source and compile it or use my bins (you still need the deps)
- fire up the wallet AS IT IS after compiling/dl'ing
- let it sync. check status with ./das-cli getinfo and compare it against the block height on the explorer
- once you are up to date check your MN status with ./das-cli masternode status
- if its not running start it with ./das-cli masternode start
- if it tells you: blah blah still syncing, restart the deamon, check the status again, if not running start it. you may have to do this a couple of times.

If this doesnt work after, lets say 20 times of trying do the above again BUT

- backup wallet and das.conf
- delete ~/.das folder
- let the wallet sync
- once its synced copy your old wallet and conf back into ~/.das

This should do it
newbie
Activity: 28
Merit: 0
I hope the developer wouldn't abandon this again just like what he did to the last coin. I hope this is not Part 2 of it. Sad

I think not because everything working fine. Just some stupids here who are on the wrong chain crying like babys.
For me everything is fine and my Masternodes get paid.

I might give it a try once the Mac wallets are released but you can't blame people for having complaints about a masternodes performance they are suppose to be solid income and kinda hard when they either crash or get on the wrong chain. Hopefully the dev can polish the performance with the next releases after they get some rest.


Ah. I see.  How do you solve?

Ah. I see. How do you solve?

The problem is the most are here really noobs. They need a tutorial for everythink. If you now how mn work and you are able to use a console than you have 0 problems here
OMG, Finally. we have an expert here. Please SIR answer my question.
I rent some hash and point it to the pool in the OP (hexpool). After hours and hours of mining (I have paid for) mr. hexpool says "hey, we are on the fork".
Mr expert, in your humble opinion, have I being fucked by hexpool?

The problem is the hexpool owner. he dont know what he is doing
And here we get to the conclusion, a lot of people (including you) know what they are doing ARE YOU HEXPOOL OWNER?
Welcome to the bitcoin world guys, meat mincer of virtual wealth.

If you've read the thread you would have noticed that we are very active in this thread. This is no scam, updating to the latest wallet just made all immature blocks orphaned (as they didn't include MN payments).

So nevertheless, chain will NOT sync from any of the 12.2 nodes - ALL 12.2 nodes report height/synced_blocks status -1 - which means they all are thinking they are still downloading blocks.


I agree.




How do you solve?

I did not solve. In my opinion there is no working chain on 12.2
newbie
Activity: 28
Merit: 0
What logo did we decided on ? I really like the red one.
newbie
Activity: 41
Merit: 0
And as people do not trust:

Code:
das@pool:~$ ./wallet/DAS-source/src/das-cli -datadir=/home/das/.das2 getpeerinfo|egrep "(subver|blocks)"
    "subver": "/Das Core:0.12.2/",
    "synced_blocks": -1,
    "subver": "/Das Core:0.12.1/",
    "synced_blocks": 16800,
    "subver": "/Das Core:0.12.2/",
    "synced_blocks": -1,
    "subver": "/Das Core:0.12.2/",
    "synced_blocks": -1,
    "subver": "/Das Core:0.12.1/",
    "synced_blocks": 16800,
    "subver": "/Das Core:0.12.1/",
    "synced_blocks": 16800,
    "subver": "/Das Core:0.12.1/",
    "synced_blocks": 16800,
    "subver": "/Das Core:0.12.1/",
    "synced_blocks": -1,
    "subver": "/Das Core:0.12.2/",
    "synced_blocks": -1,

and infinitely...

./das-cli getblocktemplate
error code: -10
error message:
Das is downloading blocks...
---------------------------------
We need again updates Smiley
newbie
Activity: 28
Merit: 0
And as people do not trust:

Code:
das@pool:~$ ./wallet/DAS-source/src/das-cli -datadir=/home/das/.das2 getpeerinfo|egrep "(subver|blocks)"
    "subver": "/Das Core:0.12.2/",
    "synced_blocks": -1,
    "subver": "/Das Core:0.12.1/",
    "synced_blocks": 16800,
    "subver": "/Das Core:0.12.2/",
    "synced_blocks": -1,
    "subver": "/Das Core:0.12.2/",
    "synced_blocks": -1,
    "subver": "/Das Core:0.12.1/",
    "synced_blocks": 16800,
    "subver": "/Das Core:0.12.1/",
    "synced_blocks": 16800,
    "subver": "/Das Core:0.12.1/",
    "synced_blocks": 16800,
    "subver": "/Das Core:0.12.1/",
    "synced_blocks": -1,
    "subver": "/Das Core:0.12.2/",
    "synced_blocks": -1,
member
Activity: 160
Merit: 10
I hope the developer wouldn't abandon this again just like what he did to the last coin. I hope this is not Part 2 of it. Sad

I think not because everything working fine. Just some stupids here who are on the wrong chain crying like babys.
For me everything is fine and my Masternodes get paid.

I might give it a try once the Mac wallets are released but you can't blame people for having complaints about a masternodes performance they are suppose to be solid income and kinda hard when they either crash or get on the wrong chain. Hopefully the dev can polish the performance with the next releases after they get some rest.


Ah. I see.  How do you solve?

Ah. I see. How do you solve?

The problem is the most are here really noobs. They need a tutorial for everythink. If you now how mn work and you are able to use a console than you have 0 problems here
OMG, Finally. we have an expert here. Please SIR answer my question.
I rent some hash and point it to the pool in the OP (hexpool). After hours and hours of mining (I have paid for) mr. hexpool says "hey, we are on the fork".
Mr expert, in your humble opinion, have I being fucked by hexpool?

The problem is the hexpool owner. he dont know what he is doing
And here we get to the conclusion, a lot of people (including you) know what they are doing ARE YOU HEXPOOL OWNER?
Welcome to the bitcoin world guys, meat mincer of virtual wealth.

If you've read the thread you would have noticed that we are very active in this thread. This is no scam, updating to the latest wallet just made all immature blocks orphaned (as they didn't include MN payments).

So nevertheless, chain will NOT sync from any of the 12.2 nodes - ALL 12.2 nodes report height/synced_blocks status -1 - which means they all are thinking they are still downloading blocks.


I agree.




How do you solve?
Jump to: