Topic: |ANN| DAS - Decentralized and Secure. Private Send. Masternodes. - page 107. (Read 153983 times)
July 25, 2017, 03:49:31 PM
dev, you need tu compile wallet and update on github, unless, fork will continue
July 25, 2017, 03:47:04 PM
Will just let it run now and get sth to eat 
Same here. Ppl need to update
i am running a windows 10 wallet how can i update there is no new wallet
The. Please disable the listen and Server in config so that you don't verify blocks. We need to get the most accepting nodes on the new version.
I just started up another node with the new version
July 25, 2017, 03:45:33 PM
Will just let it run now and get sth to eat
Same here. Ppl need to update
i am running a windows 10 wallet how can i update there is no new wallet
July 25, 2017, 03:36:45 PM
Will just let it run now and get sth to eat
Same here. Ppl need to update
July 25, 2017, 03:33:07 PM
Will just let it run now and get sth to eat
July 25, 2017, 03:29:46 PM
restarted my MN, its checking blocks and marking blocks from the last 2h as invalid
July 25, 2017, 03:21:40 PM
That's the same what I thought. But why does my wallet on newest version then accept them? Is is it because there are still a lot of old clients out there which accept them and my wallet accepts them because many other nodes do so?
iam watching the explorer and the debug log to see what it says, but atm it looks like the network is accepting blocks that dont follow the rules like: http://das.explorerz.top:3002/tx/38626d34a4dce6bd14368f614a408057e3c1ead8773f44b2aa0d4bbfc9b23d1e
we need to get all pools and MNs updated, or at least most
EDIT: masternode count down to 65 on my MN
If the majority of the masternodes are on the new version, the network should then reject all blocks without the proper payment.
July 25, 2017, 03:20:24 PM
I didnt reindex but i restarted both daemons again, logs now show das12.2, for some entries
okay... my MN now bitching about nodes not following the rules again
okay... my MN now bitching about nodes not following the rules again
July 25, 2017, 03:19:54 PM
That's the same what I thought. But why does my wallet on newest version then accept them? Is is it because there are still a lot of old clients out there which accept them and my wallet accepts them because many other nodes do so?
iam watching the explorer and the debug log to see what it says, but atm it looks like the network is accepting blocks that dont follow the rules like: http://das.explorerz.top:3002/tx/38626d34a4dce6bd14368f614a408057e3c1ead8773f44b2aa0d4bbfc9b23d1e
we need to get all pools and MNs updated, or at least most
EDIT: masternode count down to 65 on my MN
also:
https://image.prntscr.com/image/o0DMcy09QQuHu1roQGUGSA.png
Yes, that's what I thought. Also all updated nodes do show current height as -1
July 25, 2017, 03:18:13 PM
That's the same what I thought. But why does my wallet on newest version then accept them? Is is it because there are still a lot of old clients out there which accept them and my wallet accepts them because many other nodes do so?
iam watching the explorer and the debug log to see what it says, but atm it looks like the network is accepting blocks that dont follow the rules like: http://das.explorerz.top:3002/tx/38626d34a4dce6bd14368f614a408057e3c1ead8773f44b2aa0d4bbfc9b23d1e
we need to get all pools and MNs updated, or at least most
EDIT: masternode count down to 65 on my MN
i love to update my masternode..... but how i'm running on windows 10
July 25, 2017, 03:17:30 PM
I think we forked, my nodes are running on 12.2:
24.244.180.55.9399
195.181.243.208:9399
currently block 16380 while my windows wallet based on 12.1 are in the future. In case you have issues compiling the unix source -> https://github.com/whywefight/DAS-12.2 (bins only)
If your node is running on 12.2 pass me the ip ill add you to my node
EDIT: Thanks @parsec!
24.244.180.55.9399
195.181.243.208:9399
currently block 16380 while my windows wallet based on 12.1 are in the future. In case you have issues compiling the unix source -> https://github.com/whywefight/DAS-12.2 (bins only)
If your node is running on 12.2 pass me the ip ill add you to my node
EDIT: Thanks @parsec!
185.137.97.24:9399
great ill add you as node, lets get that chain moving again
I'm somehow stuck on block 16402?!
by the time writing this i am at 16434
Yes, restart helped. Nevertheless - there are still blocks without MN payment, see block 16433.
Another pool ir solominer.
@lyngaa new winwallet not released by now
Yes, but do. those blocks get rolled back? Any why is my wallet still accepting those?
Actually they should get rejected by the network as they dont fit the rules
That's the same what I thought. But why does my wallet on newest version then accept them? Is is it because there are still a lot of old clients out there which accept them and my wallet accepts them because many other nodes do so?
Restart the dasd and das-qt with the -reindex option
Network seems stable now, currently at block 16451 (at time of writing)
Congrats to the dev!!!
Block 16450 still generated without MN payment!
You're right, there is only a vout
decoderawtransaction 02000000010000000000000000000000000000000000000000000000000000000000000000fffff fff1702424004fea2775908810000328e0200007969696d7000000000000100f902950000000019 76a9140edbba42ef1b75c562927cf70220e656a50d895f88ac00000000
{
"txid": "b8af04c36e23575905d12ea751694b058837e36eb1e86eae0867af2fc9c74d04",
"size": 108,
"version": 2,
"locktime": 0,
"vin": [
{
"coinbase": "02424004fea2775908810000328e0200007969696d7000",
"sequence": 0
}
],
"vout": [
{
"value": 25.00000000,
"n": 0,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 0edbba42ef1b75c562927cf70220e656a50d895f OP_EQUALVERIFY OP_CHECKSIG",
"hex": "76a9140edbba42ef1b75c562927cf70220e656a50d895f88ac",
"reqSigs": 1,
"type": "pubkeyhash",
"addresses": [
"D6VfDtEpzY5jfJucLBepkTM4dtQmNZpHuo"
]
}
}
]
}
July 25, 2017, 03:14:23 PM
That's the same what I thought. But why does my wallet on newest version then accept them? Is is it because there are still a lot of old clients out there which accept them and my wallet accepts them because many other nodes do so?
iam watching the explorer and the debug log to see what it says, but atm it looks like the network is accepting blocks that dont follow the rules like: http://das.explorerz.top:3002/tx/38626d34a4dce6bd14368f614a408057e3c1ead8773f44b2aa0d4bbfc9b23d1e
we need to get all pools and MNs updated, or at least most
EDIT: masternode count down to 65 on my MN
also:
July 25, 2017, 03:11:21 PM
Great job dev. MN is running great. Can I create more than one ?
Yes you can but you'll need to have multiple IPs and another 1k DAS.
On Another note. Nothing but up hill from here take a day off or something Dev we don't need you getting burnt out!
It works on a raspberry too?
July 25, 2017, 03:10:31 PM
Great job dev. MN is running great. Can I create more than one ?
On one comp doesn't work more than one MN.
i was trying with this tread https://www.dash.org/forum/threads/guide-to-run-multiple-wallets-on-pc.4995/
July 25, 2017, 03:09:29 PM
Great job dev. MN is running great. Can I create more than one ?
Yes you can but you'll need to have multiple IPs and another 1k DAS.
On Another note. Nothing but up hill from here take a day off or something Dev we don't need you getting burnt out!
July 25, 2017, 03:08:56 PM
Here running also everything fine.
July 25, 2017, 03:06:56 PM
Great job dev. MN is running great. Can I create more than one ?
July 25, 2017, 03:04:20 PM
I think we forked, my nodes are running on 12.2:
24.244.180.55.9399
195.181.243.208:9399
currently block 16380 while my windows wallet based on 12.1 are in the future. In case you have issues compiling the unix source -> https://github.com/whywefight/DAS-12.2 (bins only)
If your node is running on 12.2 pass me the ip ill add you to my node
EDIT: Thanks @parsec!
24.244.180.55.9399
195.181.243.208:9399
currently block 16380 while my windows wallet based on 12.1 are in the future. In case you have issues compiling the unix source -> https://github.com/whywefight/DAS-12.2 (bins only)
If your node is running on 12.2 pass me the ip ill add you to my node
EDIT: Thanks @parsec!
185.137.97.24:9399
great ill add you as node, lets get that chain moving again
I'm somehow stuck on block 16402?!
by the time writing this i am at 16434
Yes, restart helped. Nevertheless - there are still blocks without MN payment, see block 16433.
Another pool ir solominer.
@lyngaa new winwallet not released by now
Yes, but do. those blocks get rolled back? Any why is my wallet still accepting those?
Actually they should get rejected by the network as they dont fit the rules
That's the same what I thought. But why does my wallet on newest version then accept them? Is is it because there are still a lot of old clients out there which accept them and my wallet accepts them because many other nodes do so?
Restart the dasd and das-qt with the -reindex option
Network seems stable now, currently at block 16451 (at time of writing)
Congrats to the dev!!!
Block 16450 still generated without MN payment!
July 25, 2017, 03:00:47 PM
I think we forked, my nodes are running on 12.2:
24.244.180.55.9399
195.181.243.208:9399
currently block 16380 while my windows wallet based on 12.1 are in the future. In case you have issues compiling the unix source -> https://github.com/whywefight/DAS-12.2 (bins only)
If your node is running on 12.2 pass me the ip ill add you to my node
EDIT: Thanks @parsec!
24.244.180.55.9399
195.181.243.208:9399
currently block 16380 while my windows wallet based on 12.1 are in the future. In case you have issues compiling the unix source -> https://github.com/whywefight/DAS-12.2 (bins only)
If your node is running on 12.2 pass me the ip ill add you to my node
EDIT: Thanks @parsec!
185.137.97.24:9399
great ill add you as node, lets get that chain moving again
I'm somehow stuck on block 16402?!
by the time writing this i am at 16434
Yes, restart helped. Nevertheless - there are still blocks without MN payment, see block 16433.
Another pool ir solominer.
@lyngaa new winwallet not released by now
Yes, but do. those blocks get rolled back? Any why is my wallet still accepting those?
Actually they should get rejected by the network as they dont fit the rules
That's the same what I thought. But why does my wallet on newest version then accept them? Is is it because there are still a lot of old clients out there which accept them and my wallet accepts them because many other nodes do so?
Restart the dasd and das-qt with the -reindex option
Network seems stable now, currently at block 16451 (at time of writing)
Congrats to the dev!!!
July 25, 2017, 02:54:03 PM
I think we forked, my nodes are running on 12.2:
24.244.180.55.9399
195.181.243.208:9399
currently block 16380 while my windows wallet based on 12.1 are in the future. In case you have issues compiling the unix source -> https://github.com/whywefight/DAS-12.2 (bins only)
If your node is running on 12.2 pass me the ip ill add you to my node
EDIT: Thanks @parsec!
24.244.180.55.9399
195.181.243.208:9399
currently block 16380 while my windows wallet based on 12.1 are in the future. In case you have issues compiling the unix source -> https://github.com/whywefight/DAS-12.2 (bins only)
If your node is running on 12.2 pass me the ip ill add you to my node
EDIT: Thanks @parsec!
185.137.97.24:9399
great ill add you as node, lets get that chain moving again
I'm somehow stuck on block 16402?!
by the time writing this i am at 16434
Yes, restart helped. Nevertheless - there are still blocks without MN payment, see block 16433.
Another pool ir solominer.
@lyngaa new winwallet not released by now
Yes, but do. those blocks get rolled back? Any why is my wallet still accepting those?
Actually they should get rejected by the network as they dont fit the rules
That's the same what I thought. But why does my wallet on newest version then accept them? Is is it because there are still a lot of old clients out there which accept them and my wallet accepts them because many other nodes do so?
Jump to: