Author

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

legendary
Activity: 1536
Merit: 1000
electronic [r]evolution
Dev spent 10's of thousands of dollars starting this coin? Hahahaha more BS.
Many members here will remember that I had a 28 BTC bounty for anyone capable of developing the mini-blockchain scheme:

[CLOSED] $20,000 Mini-Blockchain Implementation

Admittedly BTC was worth much more at that point in time, and I didn't spend 28 BTC on development, but it was more than 20 BTC. And so far I've only been able to mine 2 blocks myself. So I'm sorry if Windows users feel some how robbed, but there were no guarantees when you decided to use this coin and we have a big obvious red warning plastered on the website which explains how experimental this coin is.
full member
Activity: 288
Merit: 105
Can the old wallet be used?

Yeah just run the new exe. No delete/upgrade or anything required.
full member
Activity: 154
Merit: 100
I can't get a transaction from block 1 by the hash.
Can anybody check it?
What's wrong?
Couple things. It was printing the wrong txid, a what you really want to use it getrawtransaction txid 1
This is fixed in github and binaries are building.

Ok. Please, notify when the build will be available.


New binaries http://gpile.it/mbc/  800/801 vintage

Can the old wallet be used?
hero member
Activity: 597
Merit: 504
Ok we should have working Windows binaries now.

cryptonited-qt:
http://gpile.it/mbc/win64_cryptonite-qt_14072723.exe

cryptonited:
http://gpile.it/mbc/win64_cryptonited_14072723.exe

EDIT: you will probably need to delete the cryptonite folder inside of ~/AppData/Raoming/

Well dev seems to be working so far I did not re-download the dll's tho? No matter?

Still have to say the shit that went down with this launch is not cool.

OK have to take that back all my wallets just went back to 0 balance! STILL NOT WORKING. And I remove the data in roaming folder.
full member
Activity: 288
Merit: 105
I can't get a transaction from block 1 by the hash.
Can anybody check it?
What's wrong?
Couple things. It was printing the wrong txid, a what you really want to use it getrawtransaction txid 1
This is fixed in github and binaries are building.

Ok. Please, notify when the build will be available.


New binaries http://gpile.it/mbc/  800/801 vintage
full member
Activity: 212
Merit: 100
Dev spent 10's of thousands of dollars starting this coin? Hahahaha more BS.
legendary
Activity: 1610
Merit: 1008
Forget-about-it
oh my god you guys didnt get coins for 25 minutes of work, complain more!
full member
Activity: 126
Merit: 100
XC
stupid dev, refund our POWER! shit!
full member
Activity: 126
Merit: 100
This is totally a mistake dissussion thread.  Please make it right and relaunch !~!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
full member
Activity: 126
Merit: 100
XC
The windows chain is not viable. The difficulty adjustment had no effect, so all those coins were mined with minimum difficulty. Part of the problem is people thinking they lost some huge amount of coin when in fact those coins represent 1/1000 or less the work of coins done on the working chain.

So even if you have 200k XCN on that fork, it's probably not even a single blocks worth of work on the other chain. So moral of the story is that it's not practical to move the network to the windows chain and it's also not sane as the total work done in that chain is marginal at best. It seems to be a case of, well I lost mine, so everybody should lose theirs. One of these chains is correct, and the other is decidedly not. It sucks that you mined a weird chain, and I apologize for writing that code. But I am not the distributor of whatever justice you seek and am not going to tell people that the valid proof of works that they found don't count anymore because your miner was broke.

All of this was caused by a single uninitialized variable, and presumably some compiler difference caused this to not be a critical error on linux.

For those of you that think we don't want to restart to keep coins. Let me give you the lowdown. Between bitfreak and I, we have a total of 4 blocks. I'm pretty sure that in any kind of relaunch the results will be the same simply because we are pushing out the code and pushing go at the same time.




Don't waste your time to write these bullshits. Tell us how to get windows wallet work!

Dev, I wanna fuck your grandma!!! fuck off!!! shit!!!
sr. member
Activity: 300
Merit: 250
Don't waste your time to write these bullshits. Tell us how to get windows wallet work!

it's working already, i got synced without needs of adding nodes or conf file. just download wallet plus dll file and wait.
full member
Activity: 154
Merit: 100
The windows chain is not viable. The difficulty adjustment had no effect, so all those coins were mined with minimum difficulty. Part of the problem is people thinking they lost some huge amount of coin when in fact those coins represent 1/1000 or less the work of coins done on the working chain.

So even if you have 200k XCN on that fork, it's probably not even a single blocks worth of work on the other chain. So moral of the story is that it's not practical to move the network to the windows chain and it's also not sane as the total work done in that chain is marginal at best. It seems to be a case of, well I lost mine, so everybody should lose theirs. One of these chains is correct, and the other is decidedly not. It sucks that you mined a weird chain, and I apologize for writing that code. But I am not the distributor of whatever justice you seek and am not going to tell people that the valid proof of works that they found don't count anymore because your miner was broke.

All of this was caused by a single uninitialized variable, and presumably some compiler difference caused this to not be a critical error on linux.

For those of you that think we don't want to restart to keep coins. Let me give you the lowdown. Between bitfreak and I, we have a total of 4 blocks. I'm pretty sure that in any kind of relaunch the results will be the same simply because we are pushing out the code and pushing go at the same time.




Don't waste your time to write these bullshits. Tell us how to get windows wallet work!
full member
Activity: 288
Merit: 105
I got the error when click on "Inputs..." in "Coin Control Features" panel:

Coincontrol is not supported yet.
full member
Activity: 288
Merit: 105
The windows chain is not viable. The difficulty adjustment had no effect, so all those coins were mined with minimum difficulty. Part of the problem is people thinking they lost some huge amount of coin when in fact those coins represent 1/1000 or less the work of coins done on the working chain.

So even if you have 200k XCN on that fork, it's probably not even a single blocks worth of work on the other chain. So moral of the story is that it's not practical to move the network to the windows chain and it's also not sane as the total work done in that chain is marginal at best. It seems to be a case of, well I lost mine, so everybody should lose theirs. One of these chains is correct, and the other is decidedly not. It sucks that you mined a weird chain, and I apologize for writing that code. But I am not the distributor of whatever justice you seek and am not going to tell people that the valid proof of works that they found don't count anymore because your miner was broke.

All of this was caused by a single uninitialized variable, and presumably some compiler difference caused this to not be a critical error on linux.

For those of you that think we don't want to restart to keep coins. Let me give you the lowdown. Between bitfreak and I, we have a total of 4 blocks. I'm pretty sure that in any kind of relaunch the results will be the same simply because we are pushing out the code and pushing go at the same time.


hero member
Activity: 750
Merit: 511
I can't get a transaction from block 1 by the hash.
Can anybody check it?
What's wrong?
Couple things. It was printing the wrong txid, a what you really want to use it getrawtransaction txid 1
This is fixed in github and binaries are building.

Ok. Please, notify when the build will be available.

I got the error when click on "Inputs..." in "Coin Control Features" panel:
Code:
Assertion failed!
File: walletmodel.cpp, Line 554
Expression: 0
full member
Activity: 126
Merit: 100
XC
Ok we should have working Windows binaries now.

cryptonited-qt:
http://gpile.it/mbc/win64_cryptonite-qt_14072723.exe

cryptonited:
http://gpile.it/mbc/win64_cryptonited_14072723.exe

EDIT: you will probably need to delete the cryptonite folder inside of ~/AppData/Raoming/

Still cannot sync! Dev, Do I need to delete wallet.dat before launch the new wallet?
legendary
Activity: 1713
Merit: 1029
Ok we should have working Windows binaries now.

cryptonited-qt:
http://gpile.it/mbc/win64_cryptonite-qt_14072723.exe

cryptonited:
http://gpile.it/mbc/win64_cryptonited_14072723.exe

EDIT: you will probably need to delete the cryptonite folder inside of ~/AppData/Raoming/


main node Please?Huh

+1


+1

From IRC:


[22:32] <@catia> 37.187.229.12
[22:32] <@catia> 37.187.229.14
[22:32] <@catia> 5.9.84.228
full member
Activity: 211
Merit: 100
This is insane.  It's nearing 500MHashes/sec.  Is that normal 4 hours into a release?  Is it just one giant player, or several big ones?
legendary
Activity: 1713
Merit: 1029
For what it's worth, I'm a cloud miner who'd be fine with a chain reset, if it's really going to be a downfall of this coin. If you get enough interest, some of the other cloud miners might agree; it's about the long-term for the project. Just my $0.02, I'm happy to stay on the chain I mined on as well.
full member
Activity: 288
Merit: 105
I can't get a transaction from block 1 by the hash.
Can anybody check it?
What's wrong?

Couple things. It was printing the wrong txid, a what you really want to use it getrawtransaction txid 1
This is fixed in github and binaries are building.

Code:
./cryptonited getblock 0000007200edbbd3f3500fb6444e5a85ef6f5a10cced726e8d6c8b0b198dd181
{
    "hash" : "0000007200edbbd3f3500fb6444e5a85ef6f5a10cced726e8d6c8b0b198dd181",
    "confirmations" : 814,
    "height" : 1,
    "version" : 1,
    "merkleroot" : "1e08f4eff42623867148e9e80f30345c5c856840535baf9eb6c44ac6c89c7700",
    "accountroot" : "afd20cfd51ecccaffdb1ff548c31de1c388d205e4b2ec58ed3a04a4a1b744c30",
    "time" : 1406509319,
    "nonce" : 16959575210240630596,
    "difficulty" : 1.00000000,
    "chainwork" : "0000000000000000000000000000000000000000000000000000000000200000",
    "previousblockhash" : "000009a460ccc429ac6e53c91c6ed2d96697884b8b656a903042faff8971c5aa",
    "nextblockhash" : "00000151f202d968d8fa074625cb1885d78dbcfcde75a3f0e76a613fcefcb929",
    "size" : 195,
    "tx" : [
        "001f14a48874608a21d1d5e22e7255b2078cbd80fc00ee13183dac30d3e6365a"
    ]
}

Code:
./cryptonited getrawtransaction 001f14a48874608a21d1d5e22e7255b2078cbd80fc00ee13183dac30d3e6365a 1
{
    "hex" : "010000000100000000000000000000000000000000000000000036e4023602000000010036e40236020000727769474f427b8ccc2a189780593529a34cbe27000100000000000000",
    "txid" : "001f14a48874608a21d1d5e22e7255b2078cbd80fc00ee13183dac30d3e6365a",
    "version" : 1,
    "lockheight" : 1,
    "msg" : "",
    "vin" : [
        {
            "coinbase" : true,
            "pubKey" : "0000000000000000000000000000000000000000",
            "address" : "CGTta3M4t3yXu8uRgkKvaWd2d8DQvDPnpL",
            "value" : "243.1000000000ep"
        }
    ],
    "vout" : [
        {
            "value" : "243.1000000000ep",
            "n" : 0,
            "pubKey" : "27be4ca32935598097182acc8c7b424f47697772",
            "address" : "CSu8ekNgv8Dwu5tDDgW4FeJMDLXYGFb4by"
        }
    ],
    "blockhash" : "0000007200edbbd3f3500fb6444e5a85ef6f5a10cced726e8d6c8b0b198dd181",
    "confirmations" : 816,
    "time" : 1406509319,
    "blocktime" : 1406509319
}

Jump to: