Topic: [ANN][XCN] Cryptonite | 1st mini-blockchain coin | M7 PoW | No Premine - page 52. (Read 578565 times)

It seems like an old miner has been running for a few days because it looks like there is an old fork being mined or something and I suspect that is contributing to the recent sync problems which several people other than yourself have reported. Just follow the suggestions I gave a few posts ago.

That's actually a decent idea but it's more complicated than it sounds, you need to develop a protocol for proving who is a seed node and how long they've been online. You also need a way to ensure that they are actually seeding other nodes with legit data. Then you need to alter the protocol to allow those types of special rewards to be accepted by the network. Not simple at all, but it is a good idea.

I'm unsure what you mean. Cryptonite doesn't use PoS, it's purely PoW. So if you're CPU mining than your CPU usage should be 100%, else you're not taking full advantage of your CPU.

The registry changes only happen if you're using Windows, I'm not entirely sure why, but the same thing happens with Bitcoin.

Well #1 and #2 are web development things that I work on, where as #3 and #4 are core code jobs which catia works on. Although catia hasn't been able to do much work on Cryptonite lately so I'm not sure how long it will take him to get around to those issues, which is why I placed them further down the list. But you are right it's important to fix those corruption issues, it's just so hard to debug these Qt issues. One of the main reasons we are considering ditching Qt and moving over to an RPC wallet is because Qt is such a pain in the ass to debug and catia doesn't use Windows, which makes it even harder. Also keep in mind that it's very easy to backup your wallet file and/or your private keys, so even if your wallet file gets corrupted you wont lose your coins. The corruption doesn't just randomly occur either, it will only happen if you shut down Qt while it's syncing, but that's necessary some times if it wont sync.

Yeah that should be easy to fix, but small Qt issues like that are not high on our list of priorities. We may still ditch Qt in favor of an RPC based wallet.

The balloon text is from Bitcoin but it should still apply to Cryptonite. That payment request stuff creates a cryptonite URI, but you are right it doesn't appear to encode the message in the URI. I think that bug probably exists in bitcoin too.

Well I guess it's supposed to be a message from the payee to the payer, not necessarily something that the payee wants to have included in the transaction. But you are right it could be useful as a way to verify payments from specific customers.

The payment recipient (aka payee) is the one who created the URI in the first place, why would he/she want to send an encrypted message to themselves? If you're simply asking why can't the messages be encrypted, of course they can if the payer knows the full public key of the payee then he/she can encrypt the message using that public key, meaning only the payee with the private key can decrypt it. But the payer can only get the full public key if it has been used to sign transactions in the past or if it's given to the payer by the payee.

I believe that's just because the build you're using doesn't have those features enabled. You need to have the libqrencode library installed when building to make the QR code stuff work.

With the sheer number of people having wallet corruption and syncing issues (about half the posts in this thread seem to be about just that), I'd think #4 Bug Squishing should be bumped up to the #1 slot.  I'm sure there are a LOT of people who get quickly turned off from XCN after their wallet gets corrupted in the first day or two (before they get around to making a backup), and lose all their coins…people who would otherwise have become Cryptonite advocates.

In the last couple of days my qt client on win7 64bit is having problems syncing up. Has the number of full nodes dropped or am I just unlucky? Its also prone to crash since I did a resync.
On the first issue could XCN pay for full nodes in the way it pays for miners? So say every 2000 blocks it could divide a special reward of XCN to all full nodes which have been up since the last reward. This would keep the number of full nodes from dropping as in other coins like BTC. This reminds me, the CPU utilization is much higher than my blackcoin wallet even when it's staking. I assume this is either a coding issue or the M7 PoW lacks the 'ease of verification' which sha256 has? This could cause scalability issues later.
On the 2nd issue could we have an install and uninstall option or put all the config setting in a config file in the cryptonite directory rather than filling up the registry.
It's a very interesting coin which certainly fixes some of the major issues with bitcoin. Imagine being able to run a full node with no third party involved on your smartphone. But it needs to stay flexible to fix other issues as everything needs to be right for a small coin to stand a chance.

Couple things I've noticed which seem like items to be fixed in the qt client:

1. When clicking on a transaction to get details, the from field always shows 'unknown', though the information is certainly obtainable and is listed in the block explorer.
2. In payment requests, the balloon for the message field states that the message will appear when opened by the recipient's client but will not be sent with the payment. This does not appear to be true since I can't see where it's encoded. Also, why wouldn't it auto fill the message field in the recipient's payment screen? It could be useful for returning confirmation codes to prove a particular customer has a payment. However, wouldn't it also be better if the message was encrypted so that only the payment recipient could read it?

One last one, There doesn't seem to be any qr codes. They're intended to be added to the next release right?

Yes it's a common issue, usually fixed by doing a resync or adding more peers. The best way to sync is to use cryptonited instead of qt because it's much more stable. Another thing to try is to connect only to our seed node (206.72.193.148) while syncing, that worked for another person experiencing the same issue recently.

Were you able to get some help? If not check our irc channel, some of the guys there may help you.

Point 6 isn't really a high priority because you can do a resync to prune your chain. The prune command will just allow the chain to be pruned while the node is still running, instead of having to restart it. The things in point 7 aren't a high priority either because they are highly complicated and I'd rather make sure the foundation is solid before we go extending upon it.

I say skip all the other steps and go straight to 6. and 7.

They don't care

why the price so low??

The current development roadmap looks something like this:

1. web wallet improvement
  - create variant of wallet with client side encryption
  - add more extensive multi-sig transaction tools
2. block explorer improvement
  - add list of pruned blocks
  - add charts and more info
3. "slice sharing" optimization
4. bug squishing (eg wallet corruption, syncing issues)
5. consider move to rpc wallet
6. add chain pruning command
7. block mixing, side chains, etc

Is there any TODO list for this project?

I mined trough the night and then I checked the wallet and it was ok.
Now 3 hours later it shows blue squares starting 35 hours ago....
I'm on win 8.1 and never had problems. it seems not to sync,
nor it gets any mined coins since 3 hours.....
any idea what to do.....?
is it possible to put the wallet on mac after installing an syncing there the mac wallet?


ok found some help. I'm trying to get it resynced

ok resync goes until 7 days ago then it stucks with Downloading headers.....have I to wait some hours?
tried also a rescan but with same result. I have copied the wallet before. Is there a possibility to
import the copied encrypted wallet in a new wallet? I saw something in the debugwindows.
will try.

so finally got actual wallet again. opened it on os x and everything seems ok. just learned something

Can anyone help me getting a slightly modified version of Catia's cuda miner built for windows?

Link is http://github.com/spacebux-project/spacebux-cudaminer

This is for an open source pool with the reference implementation donating all 2% of profits to the cryptonite project.

Reference implementation: http://spacebux.io (currently running on testnet)
Pool source: http://github.com/spacebux-project/spacebux-pool

Yeah I'll try to get around to it some time this month. Not sure exactly how hard it's going to be but it shouldn't take me too long.

Perhaps if bitfreak gets the browser based client complete (fully encrypted), we won't need that for a while.

btw. is someone working on an android/iOs port?

@dogsAloud: thanks for the info, I'll look into it.

@mirny: try running -resync or try syncing with cryptonited.