[ANN] NoirShares UPDATE REQUIRED Advanced Features✔, Unique PoW✔

[Coindgr]

latest wallet suddenly crashed and now shows 0 connections/out of sync...

I have the same situation....

Me too.

One more with same issue...

[Mario241077]

I think the block chain was reset

{
"version" : "v0.2.3.1-beta",
"protocolversion" : 60010,
"wallets" : 1,

"stake" : 0.00000000,
"unspendable" : 0.00000000,
"balance" : 0.00000000,
"blocks" : 5,
"timeoffset" : 0,
"moneysupply" : 51.11060000,
"connections" : 0,
"proxy" : "",
"ip" : "0.0.0.0",
"difficulty" : 0.00000000,
"testnet" : false,
"paytxfee" : 0.00000000,
"mininput" : 0.00100000,
"keypoolsize" : 102,
"errors" :

[kondiomir]

I think the block chain was reset

{
"version" : "v0.2.3.1-beta",
"protocolversion" : 60010,
"wallets" : 1,

"stake" : 0.00000000,
"unspendable" : 0.00000000,
"balance" : 0.00000000,
"blocks" : 5,
"timeoffset" : 0,
"moneysupply" : 51.11060000,
"connections" : 0,
"proxy" : "",
"ip" : "0.0.0.0",
"difficulty" : 0.00000000,
"testnet" : false,
"paytxfee" : 0.00000000,
"mininput" : 0.00100000,
"keypoolsize" : 102,
"errors" :

You have sinked the wallet ?

[Frigga77]

latest wallet suddenly crashed and now shows 0 connections/out of sync...

I have the same situation....

I had the wallet up for some hours yesterday, mined some to test Lotto (which I didn't because of the transferring problem), closed it for the night and now tried to start it again (compiled in Ubuntu). It keeps crashing with: Segmentation fault (core dumped). I will try to find the logfiles.

[Billyboy402]

I think the block chain was reset

{
"version" : "v0.2.3.1-beta",
"protocolversion" : 60010,
"wallets" : 1,

"stake" : 0.00000000,
"unspendable" : 0.00000000,
"balance" : 0.00000000,
"blocks" : 5,
"timeoffset" : 0,
"moneysupply" : 51.11060000,
"connections" : 0,
"proxy" : "",
"ip" : "0.0.0.0",
"difficulty" : 0.00000000,
"testnet" : false,
"paytxfee" : 0.00000000,
"mininput" : 0.00100000,
"keypoolsize" : 102,
"errors" :

i think your right

i found the 4th block 2.222

"blocks" : 4,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.00000000,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespermin" : "No information yet. Wait at least 4 minutes after starting mining for estimate.",
"networkhashps" : 0,
"pooledtx" : 0,
"testnet" : false
}

[Frigga77]

I think the block chain was reset

{
"version" : "v0.2.3.1-beta",
"protocolversion" : 60010,
"wallets" : 1,

"stake" : 0.00000000,
"unspendable" : 0.00000000,
"balance" : 0.00000000,
"blocks" : 5,
"timeoffset" : 0,
"moneysupply" : 51.11060000,
"connections" : 0,
"proxy" : "",
"ip" : "0.0.0.0",
"difficulty" : 0.00000000,
"testnet" : false,
"paytxfee" : 0.00000000,
"mininput" : 0.00100000,
"keypoolsize" : 102,
"errors" :

i think your right

i found the 4th block 2.222

"blocks" : 4,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.00000000,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespermin" : "No information yet. Wait at least 4 minutes after starting mining for estimate.",
"networkhashps" : 0,
"pooledtx" : 0,
"testnet" : false
}

This is what happens while my wallet crashes (substituted my ipaddress by myip). Seems that the chain I try to reach is on block 239?

accepted connection 207.245.41.195:64965
send version message: version 60010, blocks=239, us=myip:33333, them=207.245.41.195:64965, peer=207.245.41.195:64965
Added time data, samples 2, offset -5 (+0 minutes)
Moving 207.245.41.195:33333 to tried
receive version message: version 60010, blocks=238, us=myip:33333, them=207.245.41.195:33333, peer=207.245.41.195:64965

if I wipe my .NoirShares folder, it also connects to that same chain, no difference there. I will add the nodes Billyboy402 gave to the config file and see if that makes a difference.

edit 1:
added NoirShares.conf with all the nodes. In that case NoirShares wallet starts without crashing, but is saying there are 232 blocks left and won't sync. If I look at getmininginfo I see that I am stuck after block 6.
So in my opinion the blockchain is not reset, but the chain won't load. Or maybe the blockchain is reset but still remembers it had 238 blocks before   Guess something odd happened at block 238.

edit 2:
Trying to start with my former wallet (the one that mined in the last chain): Crashing again with core dump. I think I got block 4 in that chain, so it should have been there unconfirmed by now after downloading the first 6 blocks.
db.log: BDB0060 PANIC: fatal region error detected; run recovery.

edit 3: Now it loads again with my wallet with my mined coins until block 238: was it a seednodes problem again?

edit 4: 5 mins later again (sry, but editing is better than typing new messages every time): tried to start the miner: crashing again at block 239, db.log tells me: BDB0060 PANIC: fatal region error detected; run recovery

In the process of deleting files, starting again, adding files etc I also saw this message several times trying to start and crashing:
************************
EXCEPTION: St13runtime_error      
CDB() : can't open database file smsgPubKeys.dat, error -30973      
NoirShares in ProcessMessages()  

I tend to get the message if I delete all in .NoirShares except for NoirShares.conf and wallet.dat. Deleting wallet.dat seems to solve that, and after that I can replace the wallet with my old wallet again.
Seems we are still stuck at block 238?

edit 5:
{
"blocks" : 238,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00000009,
"errors" : "",
"generate" : true,
"genproclimit" : 2,
"hashespermin" : 8.31875512,
"networkhashps" : 2,
"pooledtx" : 0,
"testnet" : false
}

edit 6: this is getting pathetic, after 1 hour mining again it crashes....
db.log:
BDB2506 file wallet.dat has LSN 1/1108655, past end of log at 1/1071557
BDB2507 Commonly caused by moving a database from one database environment
BDB2508 to another without clearing the database LSNs, or by removing all of
BDB2509 the log files from a database environment
BDB2516 DB_ENV->log_flush: LSN of 1/1108655 past current end-of-log of 1/1071557
BDB2517 Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
BDB0061 PANIC: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
BDB3027 wallet.dat: unable to flush page: 18
BDB4519 txn_checkpoint: failed to flush the buffer cache: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
BDB0060 PANIC: fatal region error detected; run recovery
BDB0060 PANIC: fatal region error detected; run recovery
 
edit 7:
Wallet keeps crashing once in a while, will start after deleting .NoirShares, then crash after a while again. still stuck at block 238

[barwizi]

Sorry, had to take a break a bit. Lol, the house seems to be on fire.

I'm afraid you will all have to wait. There will be no more updates until i fix everything. I have taken a snapshot of the small balances you all hold and will pay you all personally.

In that regard i will not be responding as much here until i have everything under control. I'm sorry for all this, but i think i'ts best this goes back on the table.

This may take a while as the errors seem to be runtime erros, and rather than to just keep patching, i will work on every known issue first,.

[Mario241077]

really ?? fire ?? shit you're scaring me. I think of my pc!

you simply mean the problem or?

[toldy]

In the process of deleting files, starting again, adding files etc I also saw this message several times trying to start and crashing:
************************
EXCEPTION: St13runtime_error       
CDB() : can't open database file smsgPubKeys.dat, error -30973       
NoirShares in ProcessMessages() 

I tend to get the message if I delete all in .NoirShares except for NoirShares.conf and wallet.dat. Deleting wallet.dat seems to solve that, and after that I can replace the wallet with my old wallet again.
Seems we are still stuck at block 238?

I found that starting NoirSharesd -nosmsg  helped to keep it from crashing.

So we ran for all those blocks fine, until some person out there decided to play with the secure messaging functions of the wallet, which every node began crashing.

There are evil people out there that will deliberately exploit holes in code for to gain mining advantages or to steal private keys, etc.

Taking a wallet, stuffing it full of features, and hoping it works, is a terrible design idea.

Even if it did work for a week or two, and got on exchanges, all it would take is some hacker sending out malicious smsgs messages to crash the wallet at will. It would have affected the stock price and more.

I think Barwizi should not be developing alone.  We need to find him a code auditor of some sort to find these bugs before the wrong person does.  Just because a wallet appears to kind of run, does not mean it isn't exploitable.

So the real issue here is to find a proper dev team.

[barwizi]

In the process of deleting files, starting again, adding files etc I also saw this message several times trying to start and crashing:
************************
EXCEPTION: St13runtime_error       
CDB() : can't open database file smsgPubKeys.dat, error -30973       
NoirShares in ProcessMessages() 

I tend to get the message if I delete all in .NoirShares except for NoirShares.conf and wallet.dat. Deleting wallet.dat seems to solve that, and after that I can replace the wallet with my old wallet again.
Seems we are still stuck at block 238?

I found that starting NoirSharesd -nosmsg  helped to keep it from crashing.

So we ran for all those blocks fine, until some person out there decided to play with the secure messaging functions of the wallet, which every node began crashing.

There are evil people out there that will deliberately exploit holes in code for to gain mining advantages or to steal private keys, etc.

Taking a wallet, stuffing it full of features, and hoping it works, is a terrible design idea.

Even if it did work for a week or two, and got on exchanges, all it would take is some hacker sending out malicious smsgs messages to crash the wallet at will. It would have affected the stock price and more.

I think Barwizi should not be developing alone.  We need to find him a code auditor of some sort to find these bugs before the wrong person does.  Just because a wallet appears to kind of run, does not mean it isn't exploitable.

So the real issue here is to find a proper dev team.

I think Barwizi should not be developing alone. 

You are right that i do need help. That exception is one of many , all centered around the wallet and transactions, specifically clashes with standard way they are meant to operate,  a non-conbase tx requires a tx.in, which was not considered here. and is why you get that annonying "the transaction was rejected " message :- the result of tx.in - tx.out being a negative value. since transactions are the basis of the protocol and features, i cant just disable the check, i need to make sure the generation is compatible. all the features work, the problem is in the tx area.

 

[blackxx1977]

wallet is out of sync
last block received is n.238

[miramare]

I found a long discussion. But unfortunately, I don't have time to read through it.
Anyway, I hope NRS can go further.

[ekoja]

1. wallet can't sync.
2. How can I mine on linux? Is there a miner?

[blackxx1977]

Any good news Barwizi?

[syypro]

can not sync

[barwizi]

Any good news Barwizi?

Well, for one thing i'm not working alone anymore.

I will update you on progress in 24 hours.

[miramare]

When can we start to mine?

[barwizi]

When can we start to mine?

In a few days. It takes longer to see issues on the net when i do it alone.

[Frigga77]

When can we start to mine?

In a few days. It takes longer to see issues on the net when i do it alone.

? You are saying someone is helping you with the code and now you are saying you do it alone?
What was happening at block 238? Why did things go wrong?

[barwizi]

When can we start to mine?

In a few days. It takes longer to see issues on the net when i do it alone.

? You are saying someone is helping you with the code and now you are saying you do it alone?
What was happening at block 238? Why did things go wrong?

I have someone helping me with the code, that says nothing about network testing.

UPNP is fixed and so is the last IRC issue.

there was a fork @ block 238 caused by transactions and corruption of grant database on the central node we were using

I decided that i should go it alone until further notice.