[ANN][XCN] Cryptonite | 1st mini-blockchain coin | M7 PoW | No Premine

[CryptoSporidium]

Well I guess there's no better time than Christmas to let you guys know I'm still alive.

Great to see you back bitfreak!, XCN is still one of my top5 favorite coins, it just needs a little love now. It is impressive that it survived despite your sabbatical,  that's a sign of decentralised virility,  the concept of the mini blockchain has many fans.

[1715577817]

1715577817

[1715577817]

1715577817

[1715577817]

1715577817

[1715577817]

1715577817

[1715577817]

1715577817

[Blockchain Mechanic]

What issues are they having exactly? I'm guessing the cause of the issue is one of these old bugs Cryptonite has always had, so solving those problems should solve a lot of other problems.

Hi

great idea!!! mind if i step in? kinda having trouble understanding the changes you made vis-a-vi the sync process.

[pallas]

What issues are they having exactly? I'm guessing the cause of the issue is one of these old bugs Cryptonite has always had, so solving those problems should solve a lot of other problems.

There is an issue when syncing from scratch. A bit of discussion on the last pages about this problem. Hence why there are many posts about blockchain snapshots.
Fixing it, I think, is top priority. That would greatly help with new users, and having all the exchanges back.

[dextronomous]

bitfreak, need donations, man i am ready, to donate to you, for sure.

i already paid for the first month, and reg on xcn domain name, because of the no explorer moment,

minixcnexplorer.com

happens, please tell if need help, i guess, we need your help,.

got any updates, out of the air.. ?

[bitfreak!]

@pallas: yeah the problems with syncing from scratch have existed for a long time. In my experience the best way to sync is to add a node which is already fully synced and working properly, and configured to share blocks. What exactly does syncing "from scratch" mean though? If you haven't started your XCN wallet in several months it will try to catch up by downloading all the blocks it missed but there's no guarantee any node will have blocks several months old. If you download Cryptonite for the first time or you delete your block files it wont attempt to download every block ever made, it will only download blocks from the last week, but it will download all the block headers (aka the "proof chain"). That process is also known to be fairly buggy from what I remember but I've gotten it to work many times.

@Blockchain Mechanic: well I pretty much just explained the syncing process to pallas. One of the other reasons I believe syncing is so problematic is because Cryptonite was forked from Bitcoin at a time when Bitcoin had rather crappy networking code. When syncing I believe it only downloads the blockchain from a single peer. Since then Bitcoin has obviously improved the networking code and it now downloads blocks in parallel from many different peers but Cryptonite is still stuck with that crappy code, I truly don't know why anyone would create it to work that way in the first place.

@dextronomous: yeah don't worry I'll probably put the block explorer back up, but first I need to recode it to work a bit differently. Like I said I cannot really do much until I get home but that's near the top of my to-do list.

[ExEric3]

So I can remove explorer?

Why?

Because nobody donated for server bill. and it looks bitfreak! will create explorer again.

[z00py]

here is a list of working nodes for cryptonite, which you can add to your clients or servers

Code:

addnode=122.137.254.58
addnode=151.217.230.149
addnode=178.84.34.124
addnode=183.63.48.118 
addnode=195.93.239.31 
addnode=41.176.174.13 
addnode=46.10.222.164
addnode=46.10.222.164:8253
addnode=46.105.118.15
addnode=46.4.33.74
addnode=5.157.115.132 
addnode=68.193.116.54
addnode=77.111.152.33 
addnode=84.238.242.99 
addnode=86.121.146.102
addnode=86.121.146.102:40886
addnode=87.243.249.18
addnode=91.152.120.234
addnode=92.19.251.241
addnode=99.238.163.232

looks like the network is getting healthy again.

[George5]

Happy holidays guys!

I have a problem with my wallet that keeps crashing without a reason or when I try to close it/ send coins:
http://imgur.com/a/LK3gb

Does the patch that I saw on the previous page fix the problem?
If yes, anyone could share the updated windows wallet please?

[dextronomous]

HI,

yes no worries,

you should hava A backup of wallet.dat. or keys,
you should have a downloaded copy of the blockchain, to be
able to continue downloading from there on.
so delete you'r version of the blocks folder,

put a fresh wallet.dat if wanted to be sure inside the folder. or not at all.

[OpDisp]

Hi, everybody come on coins BTC38?   

The second day is no enrollment ...

And the new dipozit address is not generating...

[enerbyte]

Hi, everybody come on coins BTC38?   

The second day is no enrollment ...

And the new dipozit address is not generating...

Same thing here, I asked them and they responded

I'm sorry, it is said that XCN to increase the circulation, we are checking, if there is no will resume work on deposits.

[oldschoolgamer]

what does that response from btc38 even mean haha , i rly do like that exchange and their support for me has been good in the past so i am sure they have the best intentions , quote - "Dears. Please deposit your coin to new address(Click deposit to get a new address). Thank you. ^_^ "  dears xD but yeah ...as you mention the new address does not generate . fingers crossed it gets fixed asap . The price on bter is shocking , is this whats known as a big dump?
   
  Really happy to see bitfreak , the original dev here , allow me to say thankyou for this coin Im guessing you have read the forum and caught up on recent things , its been a bit shakey , Im still staying hopeful things can recover . I love the mini blockchain and the m7 algorythm , it does not get near the credit it deserves ....its rly quite a shame . If you start some bounties for various things to help development I will donate within my capabilities , cheers .

[George5]

@bitfreak: https://github.com/pallas1/Cryptonite

Hi pallas,
Does this patch also fix the issue with the wallet crash that I mentioned earlier?
Thanks!

[pallas]

@bitfreak: https://github.com/pallas1/Cryptonite

Hi pallas,
Does this patch also fix the issue with the wallet crash that I mentioned earlier?
Thanks!

Sorry I don't know because I made that modification in order to compile it.

[George5]

@bitfreak: https://github.com/pallas1/Cryptonite

Hi pallas,
Does this patch also fix the issue with the wallet crash that I mentioned earlier?
Thanks!

Sorry I don't know because I made that modification in order to compile it.

Are you using compiled windows wallet? Is it crashing at some point like when you close it or try to send coins?

[pallas]

@bitfreak: https://github.com/pallas1/Cryptonite

Hi pallas,
Does this patch also fix the issue with the wallet crash that I mentioned earlier?
Thanks!

Sorry I don't know because I made that modification in order to compile it.

Are you using compiled windows wallet? Is it crashing at some point like when you close it or try to send coins?

I run Linux. Tried compiling the original sources. Had to change them as you can see on my fork.

[bitfreak!]

For those people who asked to know more about the syncing process, here's a post I made a little while back:

The main difference really comes down to the fact the Bitcoin uses transaction scripting but Cryptonite doesn't. When you sync with Bitcoin you need to download the full blockchain in order to validate it and calculate your wallet balance because the inputs and outputs link the transactions together, which makes it difficult to prune old transactions.

For that same reason it can be slow to import a new private key into a bitcoind-based wallet because it needs to rescan the blockchain to recalculate the wallet balance. And that is why you simply cannot get the balance of any address which isn't in your wallet using bitcoind. However I think they've also recently remedied this problem a little bit with watch only addresses.

But I believe bitcoind still needs to perform a rescan after importing a watch only address in order to calculate the address balance, and I believe a Bitcoin wallet with pruning enabled wouldn't be able to perform those rescans because it wouldn't have the entire transaction history required to calculate the balances, because it has pruned that data.

The release notes for Bitcoin Core 0.11.0 stated that "Block pruning is currently incompatible with running a wallet due to the fact that block data is used for rescanning the wallet and importing keys or addresses (which require a rescan.)", and I'm uncertain if the situation has improved since then but they had plans for it.

I think I read some where not too long ago that they wanted to use a hash tree structure to store the unspent outputs and maybe even balances, some what similar to the "account tree" in Cryptonite, however I believe that would still require the full blockchain to be downloaded and scanned so the tree could be built, so syncing would still be very slow.

The main advantage with Cryptonite is that transactions don't link together, so all of them can safely be forgotten after a certain period of time. Instead of having to download the full blockchain, nodes only have to download a recent portion of the blockchain along with the account tree / balance sheet, with which they can become a full node.

The real trick is that the nodes share the account tree between themselves and they're able to use data embedded into the blockchain in order to verify the validity of their copy of the account tree. When a new block is accepted, transactions in the block will cause balances in the tree to be updated among all nodes so they all have the same copy of the balance sheet.

So when a transaction is being made, there is no need to reference what may be a very old transaction like with Bitcoin, instead the inputs and outputs of a transaction will simply reference address nodes in the account tree. It's a more purely mathematical approach without all the scripting on top, closer to how a normal banking system would work.

The consequences of this approach is that the balance of any address can be cheaply computed simply by looking up the balance of that address in the account tree, which all synced nodes will have an up-to-date copy of. It also means block pruning is completely compatible with using a wallet because blockchain rescans are not necessary.

Most importantly, it means that the time required for a new node to sync is vastly reduced, because instead of needing to download every transaction which has ever occurred, they only need to download transactions from the last week or so, along with the account tree which nodes are programmed to share, and they've got all they need to be a full node.

They will never have to worry about not having some old transaction which has been pruned from their disk because those transactions will never have to be referenced again. The account tree is a self contained balance sheet which tells a node essentially everything it needs to know in order to check balances and validate transactions.

Of course there are a lot of little finicky details like the inversion database which is required for undoing changes made to the account tree in the case of forking, and I would suggest reading the Cryptonite wiki if you want a deeper understanding of how it works. I tried to keep this explanation relatively simple so that it wasn't too hard to understand.

[china998]

Block Explorers is bad??

[dextronomous]

hi china,

no no block explorer is good,

bitfreak is back that is way gooder,,
so relax, buy some @ really cheap @ now @ polo

[pallas]

Btc38 working again.