[ANN][XCN] Cryptonite - NEW Thread | 1st mini-blockchain coin | Bounties!

[kiddo]

New binary release:

https://github.com/pallas1/Cryptonite/releases

Even if the old version will continue working, everyone is encourage to update: the use of new libraries for the build increases security, performance and compatibility with newer OS versions.

Cool will update asap, thanks for the heads up dev!

[1715514566]

1715514566

[muf18]

Finally I get my hands on some Cryptonite.
Now we can swap xD.
Kidding.
Btw. counterfainted coins are black listed, and can't get to circulating supply, within network (only on chinese exchanges) yes?

Also we could make test on throughput of network and how it would handle it, with some batch scripting, if there would be some participants to it.

So guys what do you think?

[d5000]

Thanks for your efforts to list the coin at Freiexchange. Maybe they can evolve into a sort of "hidden gems exchange".

this is a side effect of mini-blockchain: if you sync from scratch and use an existing wallet, you loose information about the old transactions you did with that same wallet.
you can keep the old chain data ("blocks" folder), or use the blockchain snapshot (see first post), to recover that information.

Interesting. Would it cost a big effort to add a "database" to the wallet with information about past transactions which wouldn't get lost if the blockchain is re-synced?

One could do something similar, in a manual way, exporting the JSON data about past transactions regularly and "bundling" them to a "poor man's database", but an automatic feature would be very fine - above all for people who like or even need to do some advanced accounting, like merchants and other crypto enterprises.

[pallas]

Thanks for your efforts to list the coin at Freiexchange. Maybe they can evolve into a sort of "hidden gems exchange".

this is a side effect of mini-blockchain: if you sync from scratch and use an existing wallet, you loose information about the old transactions you did with that same wallet.
you can keep the old chain data ("blocks" folder), or use the blockchain snapshot (see first post), to recover that information.

Interesting. Would it cost a big effort to add a "database" to the wallet with information about past transactions which wouldn't get lost if the blockchain is re-synced?

One could do something similar, in a manual way, exporting the JSON data about past transactions regularly and "bundling" them to a "poor man's database", but an automatic feature would be very fine - above all for people who like or even need to do some advanced accounting, like merchants and other crypto enterprises.

A "manual" approach is already available: using the public blockchain snapshot or a backup of your own chain (which will be much smaller).
Part of the information is already saved in the wallet, we could eventually try to add the missing information so the user doesn't see an incomplete transaction data.
I wonder how much bigger the wallet file would become, though.

[d5000]

A "manual" approach is already available: using the public blockchain snapshot or a backup of your own chain (which will be much smaller).

Thanks. I don't like this approach very much because it implies some centralization - even if it's not likely that it can be abused as XCN isn't suitable for "timestamping" purposes (like Factom). For now, I would prefer to export my transactions every week.

Part of the information is already saved in the wallet, we could eventually try to add the missing information so the user doesn't see an incomplete transaction data.
I wonder how much bigger the wallet file would become, though.

That would be the approach I would favour. Maybe a separate file can be added so the wallet file isn't cluttered with transaction data?

[pallas]

A "manual" approach is already available: using the public blockchain snapshot or a backup of your own chain (which will be much smaller).

Thanks. I don't like this approach very much because it implies some centralization - even if it's not likely that it can be abused as XCN isn't suitable for "timestamping" purposes (like Factom). For now, I would prefer to export my transactions every week.

Part of the information is already saved in the wallet, we could eventually try to add the missing information so the user doesn't see an incomplete transaction data.
I wonder how much bigger the wallet file would become, though.

That would be the approach I would favour. Maybe a separate file can be added so the wallet file isn't cluttered with transaction data?

In the end it's just your blockchain data. Everyone's different because it starts collecting full tx data a couple weeks before your first use. You could backup it along with the wallet (i.e. blocks/ and trie.dat, with wallet.dat).

[muf18]

I today tried to make performance test on network, and it wasn't so favourable - I thought that with 60sec blocks, it will get at least 1 confirmation in faster time, than 10min.
I have set one time minimal fee, second time it was the highest fee (1XCN), and it was the same, I waited 8-10 min to get 1 conf, rest confirmation were faster, but 10 min for 1 conf, with empty blockchain is a little disappointing
Slimcoin is processing faster transactions, which was strange for me, because it has slower block times (90 sec).

Also wallet is quite memory hungry - on my computers it consumes 800-900mb of ram, in comparison to 600mb consumed by Slimcoin node, and 200mb by Peercoin node (all fully synchronized).

[pallas]

I today tried to make performance test on network, and it wasn't so favourable - I thought that with 60sec blocks, it will get at least 1 confirmation in faster time, than 10min.
I have set one time minimal fee, second time it was the highest fee (1XCN), and it was the same, I waited 8-10 min to get 1 conf, rest confirmation were faster, but 10 min for 1 conf, with empty blockchain is a little disappointing
Slimcoin is processing faster transactions, which was strange for me, because it has slower block times (90 sec).

Also wallet is quite memory hungry - on my computers it consumes 800-900mb of ram, in comparison to 600mb consumed by Slimcoin node, and 200mb by Peercoin node (all fully synchronized).

Confirmation time depends on hashrate, difficulty and luck.
In average, shorter block time will always be faster.
Also what is important and would be interesting to test is tx throughput.

[muf18]

I agree.
I see that in the client there is an option to sent coins to mulitply addresses, but probably it would be better to make a batch script for it.

I have bought a handful of coins to test network, but would somebody willing to test it setting up a 10-20 nodes to sent it to them simultaneously.

Without it, it's hard to test with 2-3 computers, throughput of network. I can't make a couple of VMs, but it won't be enough.

I thought this could be an alternative to DPoS, in terms of performance, but it looks like decentralization can't be scalable.
So I think in the future we will see more centralizated solutions like DPoS taking over, or Ethereum sharding, or Bitcoin second layer solution.

Just blockchain looks like in current form can't be scalable, with standard (POW/POS) consensus algorythms.

[9Bank]

what am i missing to import a XCN paper-wallet from within the new Windows wallet? i've been running 1.4.2 until today updated with the Cryptonite-0-1-5-db61.zip version.

i decided to send my XCN to a second laptop and install the db61 version (non backward compatible) then sent it back to the new empty wallet. worked fine, and still shows older transactions.

going to buy a couple Freiexchange shares too...

EDIT: next day

wasn't able to transfer from paper - changed dir to the path specified from %appdata% search. in a Windows console i entered>importprivkey [myprivatekey]

here's what Windows returned.
'importprivkey' is not recognized as an internal or external command, operable program or batch file.

[e.nexus]

what am i missing to import a XCN paper-wallet from within the new Windows wallet? i've been running 1.4.2 until today updated with the Cryptonite-0-1-5-db61.zip version.

i decided to send my XCN to a second laptop and install the db61 version (non backward compatible) then sent it back to the new empty wallet. worked fine, and still shows older transactions.

going to buy a couple Freiexchange shares too...

In console use:

importprivkey [yourprivatekey]

[kiddo]

Finally I get my hands on some Cryptonite.
Now we can swap xD.
Kidding.
Btw. counterfainted coins are black listed, and can't get to circulating supply, within network (only on chinese exchanges) yes?

Also we could make test on throughput of network and how it would handle it, with some batch scripting, if there would be some participants to it.

So guys what do you think?

Is there a swap undergoing or planned, as I hold some coins too.

[pallas]

Finally I get my hands on some Cryptonite.
Now we can swap xD.
Kidding.
Btw. counterfainted coins are black listed, and can't get to circulating supply, within network (only on chinese exchanges) yes?

Also we could make test on throughput of network and how it would handle it, with some batch scripting, if there would be some participants to it.

So guys what do you think?

Is there a swap undergoing or planned, as I hold some coins too.

We talked about a possible coin swap to have a clean blockchain. Nothing planned yet. It should go along with the rebranding.

[d5000]

I have bought a handful of coins to test network, but would somebody willing to test it setting up a 10-20 nodes to sent it to them simultaneously.

Without it, it's hard to test with 2-3 computers, throughput of network. I can't make a couple of VMs, but it won't be enough.

I am interested in such a kind of performance test and would like to participate, but in the next weeks I have not so much time for it. In mid to late April, it would be possible for me. I'll confirm in 2-3 weeks.

It would be reasonable to use a test network for that. Is there currently a XCN testnet running?

[pallas]

I have bought a handful of coins to test network, but would somebody willing to test it setting up a 10-20 nodes to sent it to them simultaneously.

Without it, it's hard to test with 2-3 computers, throughput of network. I can't make a couple of VMs, but it won't be enough.

I am interested in such a kind of performance test and would like to participate, but in the next weeks I have not so much time for it. In mid to late April, it would be possible for me. I'll confirm in 2-3 weeks.

It would be reasonable to use a test network for that. Is there currently a XCN testnet running?

I don't think so but we can quickly set it up.
Thanks.

[gnasirator]

I have bought a handful of coins to test network, but would somebody willing to test it setting up a 10-20 nodes to sent it to them simultaneously.

Without it, it's hard to test with 2-3 computers, throughput of network. I can't make a couple of VMs, but it won't be enough.

I am interested in such a kind of performance test and would like to participate, but in the next weeks I have not so much time for it. In mid to late April, it would be possible for me. I'll confirm in 2-3 weeks.

It would be reasonable to use a test network for that. Is there currently a XCN testnet running?

I don't think so but we can quickly set it up.
Thanks.

well, just using the live net would be doable, too. TX fees are literally nothing, so would be interesting to compare testnet vs live.
I'm surprised about the initial report of having 8-10 min confirmation time. Whenever I did a transfer, it was visible the same instant (sent around the world, NZ -> Germany while talking on phone) and confirmed within the next block.
Keep in mind that with withdrawal limits in place, technically, no confirmation is required and instant tx is possible. This feature needs more support in the wallet to be actually usable but the foundation is there!

[e.nexus]

I have bought a handful of coins to test network, but would somebody willing to test it setting up a 10-20 nodes to sent it to them simultaneously.

Without it, it's hard to test with 2-3 computers, throughput of network. I can't make a couple of VMs, but it won't be enough.

I am interested in such a kind of performance test and would like to participate, but in the next weeks I have not so much time for it. In mid to late April, it would be possible for me. I'll confirm in 2-3 weeks.

It would be reasonable to use a test network for that. Is there currently a XCN testnet running?

I don't think so but we can quickly set it up.
Thanks.

well, just using the live net would be doable, too. TX fees are literally nothing, so would be interesting to compare testnet vs live.
I'm surprised about the initial report of having 8-10 min confirmation time. Whenever I did a transfer, it was visible the same instant (sent around the world, NZ -> Germany while talking on phone) and confirmed within the next block.
Keep in mind that with withdrawal limits in place, technically, no confirmation is required and instant tx is possible. This feature needs more support in the wallet to be actually usable but the foundation is there!

I think when they tested the diff was high and Mr 10GH had just left.

[muf18]

I have bought a handful of coins to test network, but would somebody willing to test it setting up a 10-20 nodes to sent it to them simultaneously.

Without it, it's hard to test with 2-3 computers, throughput of network. I can't make a couple of VMs, but it won't be enough.

I am interested in such a kind of performance test and would like to participate, but in the next weeks I have not so much time for it. In mid to late April, it would be possible for me. I'll confirm in 2-3 weeks.

It would be reasonable to use a test network for that. Is there currently a XCN testnet running?

I don't think so but we can quickly set it up.
Thanks.

well, just using the live net would be doable, too. TX fees are literally nothing, so would be interesting to compare testnet vs live.
I'm surprised about the initial report of having 8-10 min confirmation time. Whenever I did a transfer, it was visible the same instant (sent around the world, NZ -> Germany while talking on phone) and confirmed within the next block.
Keep in mind that with withdrawal limits in place, technically, no confirmation is required and instant tx is possible. This feature needs more support in the wallet to be actually usable but the foundation is there!

I don't know why it was like that maybe ot confirmed faster, but in client it showed first confirmation after 8 min, and I checked it. 5 confirmations more come in 5 min, so it was strange.
Btw. do you think that if it would be rebranded, you could change from PoW to PoS? I mean 4 years distrubution is a lot, and PoS could be more robust, and more energy efficient.

[e.nexus]

I have bought a handful of coins to test network, but would somebody willing to test it setting up a 10-20 nodes to sent it to them simultaneously.

Without it, it's hard to test with 2-3 computers, throughput of network. I can't make a couple of VMs, but it won't be enough.

I am interested in such a kind of performance test and would like to participate, but in the next weeks I have not so much time for it. In mid to late April, it would be possible for me. I'll confirm in 2-3 weeks.

It would be reasonable to use a test network for that. Is there currently a XCN testnet running?

I don't think so but we can quickly set it up.
Thanks.

well, just using the live net would be doable, too. TX fees are literally nothing, so would be interesting to compare testnet vs live.
I'm surprised about the initial report of having 8-10 min confirmation time. Whenever I did a transfer, it was visible the same instant (sent around the world, NZ -> Germany while talking on phone) and confirmed within the next block.
Keep in mind that with withdrawal limits in place, technically, no confirmation is required and instant tx is possible. This feature needs more support in the wallet to be actually usable but the foundation is there!

I don't know why it was like that maybe ot confirmed faster, but in client it showed first confirmation after 8 min, and I checked it. 5 confirmations more come in 5 min, so it was strange.
Btw. do you think that if it would be rebranded, you could change from PoW to PoS? I mean 4 years distrubution is a lot, and PoS could be more robust, and more energy efficient.

With 1 minute block times, when the global hash drops by 85% it will take that long until the diff lowers.

[gnasirator]

I have bought a handful of coins to test network, but would somebody willing to test it setting up a 10-20 nodes to sent it to them simultaneously.

Without it, it's hard to test with 2-3 computers, throughput of network. I can't make a couple of VMs, but it won't be enough.

I am interested in such a kind of performance test and would like to participate, but in the next weeks I have not so much time for it. In mid to late April, it would be possible for me. I'll confirm in 2-3 weeks.

It would be reasonable to use a test network for that. Is there currently a XCN testnet running?

I don't think so but we can quickly set it up.
Thanks.

well, just using the live net would be doable, too. TX fees are literally nothing, so would be interesting to compare testnet vs live.
I'm surprised about the initial report of having 8-10 min confirmation time. Whenever I did a transfer, it was visible the same instant (sent around the world, NZ -> Germany while talking on phone) and confirmed within the next block.
Keep in mind that with withdrawal limits in place, technically, no confirmation is required and instant tx is possible. This feature needs more support in the wallet to be actually usable but the foundation is there!

I don't know why it was like that maybe ot confirmed faster, but in client it showed first confirmation after 8 min, and I checked it. 5 confirmations more come in 5 min, so it was strange.
Btw. do you think that if it would be rebranded, you could change from PoW to PoS? I mean 4 years distrubution is a lot, and PoS could be more robust, and more energy efficient.

With 1 minute block times, when the global hash drops by 85% it will take that long until the diff lowers.

Ah yes, Mr 10 GH could've been the culprit there ...
Nevertheless, the tx should appear as unconfirmed pretty much right away.