Author

Topic: [ANN][CRW] CROWN (SHA256) | Platform | Governance | Systemnodes | Masternodes | - page 145. (Read 316951 times)

legendary
Activity: 964
Merit: 1000
crownd updated to

    "version" : 120061,
    "protocolversion" : 70040,
    "walletversion" : 61000,

auxminingaddr=16y2K87ZZUB6edz7YGo5Ce11gMykTDgRvn

pool.cryptominer.co.uk



I've gotten Chainz to update the explorer and add you to the list Smiley If there are any other pools that would like to be added just set your address using "auxminingaddr=" in your crown.conf file and post here with the link to your pool
newbie
Activity: 6
Merit: 0
crownd updated to

    "version" : 120061,
    "protocolversion" : 70040,
    "walletversion" : 61000,

auxminingaddr=16y2K87ZZUB6edz7YGo5Ce11gMykTDgRvn

pool.cryptominer.co.uk

hero member
Activity: 805
Merit: 500
Seems like network is stabilizing nicely, we can cautiously claim our Core updates to Bitcoin 0.10 and Dash 0.12 were a success.

Monday tomorrow we are proceeding with a major PR announcement consisting of sending our progress and whitepapers to all major Bitcoin news sites and starting our twitter campaign.
hero member
Activity: 805
Merit: 500
http://prntscr.com/e7dovd *wink wink* *nudge nudge* progress Wink

Very nice mate! This will help me out so much personally.


I also like the name Crownpay, I think this could spread the use of Crown nicely. Progress here

https://github.com/Crowndev/coinomi-android/releases/tag/v1.0.0
legendary
Activity: 1092
Merit: 1000
http://prntscr.com/e7dovd *wink wink* *nudge nudge* progress Wink

Very nice mate! This will help me out so much personally.
legendary
Activity: 964
Merit: 1000
************************
EXCEPTION: St12out_of_range      
CInv::GetCommand() : type=15 unknown type      
crowncoin in ProcessMessages()      

Looks like your connected to the old 0.9.3.5 nodes which means you need to update your wallet to 0.12.0.61
can you also please claim your address using
auxminingaddr=
in your crown.conf file. Please post that address when your done, and ill get it added to chainz

Did you have a chance to set your mining address? Please claim your address when possible. It will also help with advertisement to your pool, people on the block explorer will be able to see which blocks are mined by you with a link to your pool.
hero member
Activity: 805
Merit: 500
legendary
Activity: 964
Merit: 1000
Ok thank you, Will wait patiently.

https://github.com/Crowndev/crowncoin/tree/fix-hot-throne

Give that a shot now. I was able to successfully broadcast and see the node from my windows wallet. I've done a few things that should've helped with the issue.
ACP
hero member
Activity: 612
Merit: 520
Ok thank you, Will wait patiently.
legendary
Activity: 964
Merit: 1000
Just setup a fresh linux vm in under 10 minutes, syncing now.
Welcome to Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-22-generic x86_64)

Code:
#!/bin/bash
curl -sSL https://github.com/Crowndev/crowncoin/releases/download/v0.12.0.61/crown-177.6-x86_64-unknown-linux-gnu.tar.gz -o crown.tgz
tar xzf crown.tgz --no-anchored crownd crown-cli --transform='s/.*\///'
sudo mv crownd crown-cli /usr/bin/
rm -rf crown*

fully synced in less than 30
{
    "version" : 120061,
    "protocolversion" : 70040,
    "walletversion" : 61000,
    "balance" : 10000.00000000,
    "darksend_balance" : 0.00000000,
    "blocks" : 1250390,
    "timeoffset" : 0,
    "connections" : 12,
    "proxy" : "",
    "difficulty" : 13494045.78497791,
    "testnet" : false,
    "keypoololdest" : 1486869903,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00010000,
    "errors" : ""
}
Sat Feb 11 22:49:38 EST 2017


Found the fix and the issue for the hot throne, nothing too major and I can release a client fix for it shortly. Going to talk to the team to see if they would like to make a release for it or not, but it will not require everyone to update. to put everyones mind at ease Wink

https://github.com/Crowndev/crowncoin/tree/fix-hot-throne


Alright guys just going to put this out here. If you find an issue with something and your certain your config is okay. Then check the Dash github. https://github.com/dashpay/dash and type a short statement explaining the issue. With the last one being "hot node" if you search that you'll see that there was a PR merged into dash 0.12.1.x to fix the issue with hot nodes.

It's a bit easier on me, since I to try and recreate and track the issue before I consider it an issue. If someone points me right toward the fix it's much easier to get implemented at a quicker pace Smiley
]
So we can work with the above fix now? re: https://github.com/Crowndev/crowncoin/tree/fix-hot-throne

just testing it now myself to see If everything is alright. Found another addition made to dash that should help with the hot nodes.
ACP
hero member
Activity: 612
Merit: 520
Just setup a fresh linux vm in under 10 minutes, syncing now.
Welcome to Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-22-generic x86_64)

Code:
#!/bin/bash
curl -sSL https://github.com/Crowndev/crowncoin/releases/download/v0.12.0.61/crown-177.6-x86_64-unknown-linux-gnu.tar.gz -o crown.tgz
tar xzf crown.tgz --no-anchored crownd crown-cli --transform='s/.*\///'
sudo mv crownd crown-cli /usr/bin/
rm -rf crown*

fully synced in less than 30
{
    "version" : 120061,
    "protocolversion" : 70040,
    "walletversion" : 61000,
    "balance" : 10000.00000000,
    "darksend_balance" : 0.00000000,
    "blocks" : 1250390,
    "timeoffset" : 0,
    "connections" : 12,
    "proxy" : "",
    "difficulty" : 13494045.78497791,
    "testnet" : false,
    "keypoololdest" : 1486869903,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00010000,
    "errors" : ""
}
Sat Feb 11 22:49:38 EST 2017


Found the fix and the issue for the hot throne, nothing too major and I can release a client fix for it shortly. Going to talk to the team to see if they would like to make a release for it or not, but it will not require everyone to update. to put everyones mind at ease Wink

https://github.com/Crowndev/crowncoin/tree/fix-hot-throne


Alright guys just going to put this out here. If you find an issue with something and your certain your config is okay. Then check the Dash github. https://github.com/dashpay/dash and type a short statement explaining the issue. With the last one being "hot node" if you search that you'll see that there was a PR merged into dash 0.12.1.x to fix the issue with hot nodes.

It's a bit easier on me, since I to try and recreate and track the issue before I consider it an issue. If someone points me right toward the fix it's much easier to get implemented at a quicker pace Smiley
]
So we can work with the above fix now? re: https://github.com/Crowndev/crowncoin/tree/fix-hot-throne
legendary
Activity: 964
Merit: 1000
Just setup a fresh linux vm in under 10 minutes, syncing now.
Welcome to Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-22-generic x86_64)

Code:
#!/bin/bash
curl -sSL https://github.com/Crowndev/crowncoin/releases/download/v0.12.0.61/crown-177.6-x86_64-unknown-linux-gnu.tar.gz -o crown.tgz
tar xzf crown.tgz --no-anchored crownd crown-cli --transform='s/.*\///'
sudo mv crownd crown-cli /usr/bin/
rm -rf crown*

fully synced in less than 30
{
    "version" : 120061,
    "protocolversion" : 70040,
    "walletversion" : 61000,
    "balance" : 10000.00000000,
    "darksend_balance" : 0.00000000,
    "blocks" : 1250390,
    "timeoffset" : 0,
    "connections" : 12,
    "proxy" : "",
    "difficulty" : 13494045.78497791,
    "testnet" : false,
    "keypoololdest" : 1486869903,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00010000,
    "errors" : ""
}
Sat Feb 11 22:49:38 EST 2017


Found the fix and the issue for the hot throne, nothing too major and I can release a client fix for it shortly. Going to talk to the team to see if they would like to make a release for it or not, but it will not require everyone to update. to put everyones mind at ease Wink

https://github.com/Crowndev/crowncoin/tree/fix-hot-throne


Alright guys just going to put this out here. If you find an issue with something and your certain your config is okay. Then check the Dash github. https://github.com/dashpay/dash and type a short statement explaining the issue. With the last one being "hot node" if you search that you'll see that there was a PR merged into dash 0.12.1.x to fix the issue with hot nodes.

It's a bit easier on me, since I to try and recreate and track the issue before I consider it an issue. If someone points me right toward the fix it's much easier to get implemented at a quicker pace Smiley
legendary
Activity: 964
Merit: 1000
legendary
Activity: 964
Merit: 1000
member
Activity: 84
Merit: 10
newbie
Activity: 6
Merit: 0
EXCEPTION: St12out_of_range      
CInv::GetCommand() : type=15 unknown type      
crowncoin in ProcessMessages()  

Has anyone seen this or any idea of what is causing it?

EXCEPTION: St12out_of_range       
CInv::GetCommand() : type=15 unknown type       
crowncoin in ProcessMessages()       

2017-02-12 00:46:20 ProcessMessage(inv, 37 bytes) FAILED
2017-02-12 00:46:20

************************
EXCEPTION: St12out_of_range       
CInv::GetCommand() : type=14 unknown type       
crowncoin in ProcessMessages()       

2017-02-12 00:46:20 ProcessMessage(inv, 37 bytes) FAILED
2017-02-12 00:46:21 ProcessMessages(mnw, 137 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2017-02-12 00:46:21 ProcessMessage(mnw, 137 bytes) FAILED
2017-02-12 00:46:21 CheckBlock() : Using non-specific throne payments 1250218
2017-02-12 00:46:21 CheckBlock() : Found payment(1|400000000) or payee(1|3QJmnh) nHeight 1250218.
2017-02-12 00:46:21 CheckBlock() : Using non-specific throne payments 1250218
2017-02-12 00:46:21 CheckBlock() : Found payment(1|400000000) or payee(1|3QJmnh) nHeight 1250218.
2017-02-12 00:46:21 UpdateTip: new best=0bf1b97508f8dd8bc57cf2151b01fe4a8e25410f1a7039e3ee79487509cd768c  height=1250218  log2_work=73.564956  tx=1313247  date=2017-02-12 00:44:57 progress=1.000000
2017-02-12 00:46:21 ProcessBlock: ACCEPTED
2017-02-12 00:46:21 ProcessMessages(mnw, 137 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2017-02-12 00:46:21 ProcessMessage(mnw, 137 bytes) FAILED
2017-02-12 00:46:21 ProcessMessages(mnw, 137 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2017-02-12 00:46:21 ProcessMessage(mnw, 137 bytes) FAILED
2017-02-12 00:46:21 Throne payment to 1FmYfPNcKWp6uQnVgmcz1tewHkKHZBfZYN
2017-02-12 00:46:21 CreateNewBlock(): total size 1000
2017-02-12 00:46:21  Payments size:  2
2017-02-12 00:46:21  Payouts: 3QJmnh :-, 600000000  number : 0
2017-02-12 00:46:21  Payouts: 1FmYfPNcKWp6uQnVgmcz1tewHkKHZBfZYN :-, 400000000  number : 1
2017-02-12 00:46:21 CheckBlock() : Using non-specific throne payments 1250219
2017-02-12 00:46:21 CheckBlock() : Found payment(1|400000000) or payee(1|3QJmnh) nHeight 1250219.
2017-02-12 00:46:21 Throne payment to 1FmYfPNcKWp6uQnVgmcz1tewHkKHZBfZYN
2017-02-12 00:46:21 CreateNewBlock(): total size 1000
2017-02-12 00:46:21  Payments size:  2
2017-02-12 00:46:21  Payouts: 1CudxMYJNa7gqo6MEy4CrNgZLXNzoQ1pRE :-, 600000000  number : 0
2017-02-12 00:46:21  Payouts: 1FmYfPNcKWp6uQnVgmcz1tewHkKHZBfZYN :-, 400000000  number : 1
2017-02-12 00:46:21 CheckBlock() : Using non-specific throne payments 1250219
2017-02-12 00:46:21 CheckBlock() : Found payment(1|400000000) or payee(1|3QJmnh) nHeight 1250219.
2017-02-12 00:46:21 ProcessMessages(mnw, 137 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2017-02-12 00:46:21 ProcessMessage(mnw, 137 bytes) FAILED
2017-02-12 00:46:21 ProcessMessages(mnw, 137 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2017-02-12 00:46:21 ProcessMessage(mnw, 137 bytes) FAILED
2017-02-12 00:46:21 ProcessMessages(mnw, 137 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2017-02-12 00:46:21 ProcessMessage(mnw, 137 bytes) FAILED
2017-02-12 00:46:21 ProcessMessages(mnw, 137 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2017-02-12 00:46:21 ProcessMessage(mnw, 137 bytes) FAILED


************************
EXCEPTION: St12out_of_range       
CInv::GetCommand() : type=15 unknown type       
crowncoin in ProcessMessages()       

2017-02-12 00:46:27

************************
EXCEPTION: St12out_of_range       
CInv::GetCommand() : type=15 unknown type       
crowncoin in ProcessMessages()       

2017-02-12 00:46:27 ProcessMessage(inv, 37 bytes) FAILED
2017-02-12 00:46:28 receive version message: /Crown Core:0.12.0.61/: version 70040, blocks=1250218, us=138.201.65.88:9340, them=81.2.250.160:9340, peer=81.2.250.160:44208
2017-02-12 00:46:28 Added time data, samples 17, offset -6 (+0 minutes)
2017-02-12 00:46:28 nTimeOffset = -6  (+0 minutes)
2017-02-12 00:46:46 Misbehaving: 158.69.88.8:9340 (0 -> 1)
2017-02-12 00:46:46 ProcessMessage(reject, 42 bytes) FAILED
2017-02-12 00:46:46 Misbehaving: 158.69.88.8:9340 (1 -> 2)
2017-02-12 00:46:46 ProcessMessage(ping, 8 bytes) FAILED
2017-02-12 00:46:46 Misbehaving: 158.69.88.8:9340 (2 -> 3)
2017-02-12 00:46:46 ProcessMessage(getheaders, 1061 bytes) FAILED
2017-02-12 00:46:46 socket recv error Connection reset by peer (104)
2017-02-12 00:46:47 Misbehaving: 78.28.250.81:9340 (0 -> 1)
2017-02-12 00:46:47 ProcessMessage(reject, 42 bytes) FAILED
2017-02-12 00:46:47 Misbehaving: 78.28.250.81:9340 (1 -> 2)
2017-02-12 00:46:47 ProcessMessage(ping, 8 bytes) FAILED
2017-02-12 00:46:47 Misbehaving: 78.28.250.81:9340 (2 -> 3)
2017-02-12 00:46:47 ProcessMessage(getheaders, 1061 bytes) FAILED
2017-02-12 00:46:47 Misbehaving: 85.255.2.60:9340 (0 -> 1)
2017-02-12 00:46:47 ProcessMessage(reject, 42 bytes) FAILED
2017-02-12 00:46:47 Misbehaving: 85.255.2.60:9340 (1 -> 2)
2017-02-12 00:46:47 ProcessMessage(ping, 8 bytes) FAILED
2017-02-12 00:46:47 Misbehaving: 85.255.2.60:9340 (2 -> 3)
2017-02-12 00:46:47 ProcessMessage(getheaders, 1061 bytes) FAILED
2017-02-12 00:46:58

************************
EXCEPTION: St12out_of_range       
CInv::GetCommand() : type=15 unknown type       
crowncoin in ProcessMessages()       



************************
EXCEPTION: St12out_of_range       
CInv::GetCommand() : type=15 unknown type       
crowncoin in ProcessMessages()       

2017-02-12 00:46:58 ProcessMessage(inv, 37 bytes) FAILED


************************
EXCEPTION: St12out_of_range       
CInv::GetCommand() : type=15 unknown type       
crowncoin in ProcessMessages()       

2017-02-12 00:47:02

************************
EXCEPTION: St12out_of_range       
CInv::GetCommand() : type=15 unknown type       
crowncoin in ProcessMessages()       

2017-02-12 00:47:02 ProcessMessage(inv, 37 bytes) FAILED
2017-02-12 00:47:06 connect() to 99.183.197.174:9340 failed after select(): No route to host (113)
2017-02-12 00:47:07 socket recv error Connection reset by peer (104)
^C
miner@daemon4:~/.crowncoin$

************************
EXCEPTION: St12out_of_range       
CInv::GetCommand() : type=15 unknown type       
crowncoin in ProcessMessages()       



************************
EXCEPTION: St12out_of_range       
CInv::GetCommand() : type=15 unknown type       
crowncoin in ProcessMessages()       



************************
EXCEPTION: St12out_of_range       
CInv::GetCommand() : type=15 unknown type       
crowncoin in ProcessMessages()       



************************
EXCEPTION: St12out_of_range       
CInv::GetCommand() : type=15 unknown type       
crowncoin in ProcessMessages()       



************************
EXCEPTION: St12out_of_range       
CInv::GetCommand() : type=15 unknown type       
crowncoin in ProcessMessages()       
legendary
Activity: 1092
Merit: 1000
I've knocked up more spacific guides for Ubuntu 16.10 and 16.04.
If you would like to create an OS spacific guide using the ones below as a template, we can arrange a bounty.

[THRONES]


     


legendary
Activity: 964
Merit: 1000
You should be able to setup a hot node using by adding the throne options to the crown.conf file. Shouldn't need the throne.conf at all for a hot node. Make sure to use an external IP address that has port forwarding enabled to port 9340. I need to get some sleep before i start debugging anymore. I've been working on the pool to try and get it ready for Crown payments Wink

throne=1
throneaddr=
throneprivkey=

I've all that in my .crown/crown.conf.  The server is a VPS, so its IP is public and there's no firewall or anything else that would block the port.  In fact, I have 80 connections, including many incoming ones; I also verified that I can telnet to the address/port combination (51.254.131.226:9340).  This used to work with the old client, and I haven't since touched the configs or the network configuration at all.
Same problem,

Working on it now, The VPS, does it have the funds stored on it as a hot node? or are you storing the funds locally? Just about to try and set one up myself now.


Everything is ran on the vps, because we have many thrones and many vpsSame problem,
(edit) I'm getting incorrect port for mainnet but I have many connections and conifg is same. Let me guess, regenerate the throne because of the fork?


You shouldn't need to regenerate inputs because of the fork, if you have multiple vps' you could try switching to a cold node setup? It would give you a bit better security, and the ability to control all of the thrones from a single wallet, rather than having to navigate to each of the VPS' to start them if they go down.

That won't fix the hotnode problem, but i'm just about done my coffee, and getting into everything now. I'll let you guys know what i find.

Right ! finally recreated, just working on finding the issue now.
ACP
hero member
Activity: 612
Merit: 520
 sudo ./crown-cli throne start             Not capable throne: Invalid port: 0 - only 9340 is supported on mainnet.
ACP
hero member
Activity: 612
Merit: 520
You should be able to setup a hot node using by adding the throne options to the crown.conf file. Shouldn't need the throne.conf at all for a hot node. Make sure to use an external IP address that has port forwarding enabled to port 9340. I need to get some sleep before i start debugging anymore. I've been working on the pool to try and get it ready for Crown payments Wink

throne=1
throneaddr=
throneprivkey=

I've all that in my .crown/crown.conf.  The server is a VPS, so its IP is public and there's no firewall or anything else that would block the port.  In fact, I have 80 connections, including many incoming ones; I also verified that I can telnet to the address/port combination (51.254.131.226:9340).  This used to work with the old client, and I haven't since touched the configs or the network configuration at all.
Same problem,

Working on it now, The VPS, does it have the funds stored on it as a hot node? or are you storing the funds locally? Just about to try and set one up myself now.


Everything is ran on the vps, because we have many thrones and many vpsSame problem,
(edit) I'm getting incorrect port for mainnet but I have many connections and conifg is same. Let me guess, regenerate the throne because of the fork?
Jump to: