...
hi mate.. something is not right, it will not convert unless it's converting an old chain... are you certain you unzipped the downloaded chain into that directory?
if you delete all your old chain from that directory is it all recreated and starts downloading from scratch?

jsut re-read.. you must not have unzipped the chain into the correct data folder.. the downloaded chain won't convert (already done)

Available Supply  984,134,461 MYR
WHY?

I can't right now but in a few hours I can. However I would suggest you try running cryptonite on a different computer or different operating system. Some Windows machines seem to have problems running cryptonite but it's usually just qt. How do you know that cryptonited was getting stuck too?

I restarted the wallet and synced fine after i added the new nodes.
It takes a long time before the program actually starts find the nodes
But i am not sure if hirocoin will come back from the dead, there is no exchange and nobody seems to have a interrest to get action going

I'm not sure where that information is coming from, it is incorrect. There would be no reason for atomic swap transactions to require more confirmations than any other payment transaction, so something like 6 would be a safe upper bound for even very high-value trades (and less confirmations can be used for smaller value transactions).

And any contract protocol that relies on third-parties as escrow or delegates is really a hack and not a very clean way to work with cryptocurrency. Protocols like that are also weak as any third-party can be bribed or be a sybil node.

BlockStream's design for sidechains relies on atomic cross-chain swaps with a very similar protocol to what is being used in Mercury, and their judgement is probably the most trustworthy in the cryptocurrency space. (See http://www.blockstream.com/sidechains.pdf, page 21).

It's not about memory, it have 16GB (enough for Monero), and I do not use max core power ( 8 ), I am using 75% ( 6 ).
It's Ubuntu and it have all it needs to mine XMR. I use the same config and miner on the other VPS and there is no problem of any kind. So it is kinda strange to me and thats why I am asking for help or solution.

That's not the problem, kiklo.

If you send coins with computer 1, computer 2 does not know a possible new generated change (back) address. After some time, you have 2 different wallets with a different coin amount and many different key pairs. It ends up in chaos.
A wallet is a container for many private and public keys - like a key chain. Amount of coins is a summation of all addresses.

Just the opposite:
NXT has one private and one public key. You can use it where ever you want - simultaneously.

Yet another milestone... DOGED is number 5 in network hashrate (Scrypt) LiteCoin, DogeCoin, ViaCoin, SysCoin and Doged. Very select club!

NXT didn't release the source code at first. Eventually it got released, but it was closed source to begin with.

I'm glad Satoshi didn't have this attitude.

I'm seeding this new one, but in the future it would be a good idea to include the date in the package name.

same here, i personally doesn't like audio missive. I'm not good at listening English, i had to come here in seeking for a detailed text.

What i mean is, its probably easier and common to access a forum through a full domain, rather than a subdomain. Newusers want things as quick, and easy as possible.

Yeah. I just wish it would've happened maybe 2 days earlier. After an entire year of holding I got scared and dumped everything because one key person decided to delete his profile for some reason. Now I have nothing.

Over 500k xmr on the ask book. Most I've seen since the xmr market opened there. Lots of coins on polo and someones jammed a 100k ask in at 0.00225. The games begin.

Wow... 
Someone was mining Monero with 100 times faster mining program than the rest of the miners? And controlled 60% of the network hash rate at some point?

 

The more I looked at it, the more clear it became:  The original developers deliberately crippled the miner.  It wasn't just slow, and it wasn't just naive;  it was deliberately obfuscated and made slow by the use of completely superfluous copies, function calls, use of 8 bit pointer types, and accompanied by the most ridiculously slow implementation of the AES encryption algorithm one could imagine.

But when Bytecoin was released, it was presented as though it emerged from two years on the "dark web" (Tor onion sites and the like), during which time, 80% of the possible coins that could ever be minted, had been minted.  The reception in the cryptocurrency community was heavily skeptical.

My strong belief is that the skepticism was warranted: Here's the original slow-hash from bytecoin as it was copied into Bitmonero.  It has some doozies.  For example, on line 100, you might note that for every iteration through an inner loop repeated tens of thousands of times, the AES key is re-imported into the library.  The later loop, starting on line 113, is repeated half a million times, and is so abstracted through lots of memcpys and pointer manipulation it's hard to tell that all it really does is one round of AES encryption, a pointer dereference into a random scratchpad, a 64 bit multiplication, and another pointer dereference.  Phew.  This original code was roughly 50x slower than my final optimized code, and could have easily been used to fake two years of blockchain data on a single computer or a small cluster.  I'm pretty sure that's what happened.