cGk3X4VwX4JNWAJYdPv7D5ueXg1xuATdyh
Sent you some.Code:
cE69QgmLESqkX5F7TdJFVRvijfYzF6p88H
Topic: [TEST RELEASE] Cryptonite binary for linux (NEW: Qt and Windows builds) - page 7. (Read 19296 times)
July 22, 2014, 02:50:07 PM
July 22, 2014, 02:40:48 PM
cGk3X4VwX4JNWAJYdPv7D5ueXg1xuATdyh
July 22, 2014, 02:34:35 PM
don't forget to post your address for abuse test tx's
July 22, 2014, 02:19:55 PM
Yes, I think I'm synced up now too. Are you guys on block 600s-ish?
Yep. July 22, 2014, 02:18:28 PM
Yes, I think I'm synced up now too. Are you guys on block 600s-ish?
July 22, 2014, 02:13:31 PM
The testnet chain has been reset, so several things need to happen.
1. Need new binary!
2. Must delete entire data folder before running!
3. You probably got banned from the server, so let me know when you have 1 and 2 finished and I will clear the bans.
1. Need new binary!
2. Must delete entire data folder before running!
3. You probably got banned from the server, so let me know when you have 1 and 2 finished and I will clear the bans.
All that was already done, but i guess it was something to do with the ban. All seems to be working fine now.
July 22, 2014, 02:06:59 PM
The testnet chain has been reset, so several things need to happen.
1. Need new binary!
2. Must delete entire data folder before running!
3. You probably got banned from the server, so let me know when you have 1 and 2 finished and I will clear the bans.
1. Need new binary!
2. Must delete entire data folder before running!
3. You probably got banned from the server, so let me know when you have 1 and 2 finished and I will clear the bans.
1. Check
2. I deleted everything in ~/.cryptonite except for cryptonite.conf
Is that cool? That's when I got the output above
July 22, 2014, 02:02:41 PM
The testnet chain has been reset, so several things need to happen.
1. Need new binary!
2. Must delete entire data folder before running!
3. You probably got banned from the server, so let me know when you have 1 and 2 finished and I will clear the bans.
1. Need new binary!
2. Must delete entire data folder before running!
3. You probably got banned from the server, so let me know when you have 1 and 2 finished and I will clear the bans.
July 22, 2014, 02:02:14 PM
That means Banned!
Make sure new build and new files including wallet
Make sure new build and new files including wallet
July 22, 2014, 01:45:28 PM
Same problem here.
July 22, 2014, 01:29:01 PM
What does this mean, it says Finalize Node over and over, but is still at block 0 when I getinfo
./cryptonited -testnet
Cryptonite server starting
:~# Opening /root/.cryptonite/testnet3/trie.dat
activeHeight: -1, headersHeight: -1
indexSize: 0, orphansSize: 0
askedSize: 0, missingSize: 0
validSize: 0
activeHeight: -1, headersHeight: -1
indexSize: 0, orphansSize: 0
askedSize: 0, missingSize: 0
validSize: 0
Accept block header
Update: -1 -1000 -1000 0 0
Update: 128 -1000 -1000 0 0
OS 0 NS 1
Accepted block 0
OS 1 NS 1
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
./cryptonited -testnet
Cryptonite server starting
:~# Opening /root/.cryptonite/testnet3/trie.dat
activeHeight: -1, headersHeight: -1
indexSize: 0, orphansSize: 0
askedSize: 0, missingSize: 0
validSize: 0
activeHeight: -1, headersHeight: -1
indexSize: 0, orphansSize: 0
askedSize: 0, missingSize: 0
validSize: 0
Accept block header
Update: -1 -1000 -1000 0 0
Update: 128 -1000 -1000 0 0
OS 0 NS 1
Accepted block 0
OS 1 NS 1
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
Finalize Node
July 22, 2014, 11:22:56 AM
Testnet currently offline. We are resetting the chain to change block reward amount. So you will need new binaries to get back online. These should be up along with the network in about 2 hours.
Edit: New binaries are up and new chain running. Currently at block 90.
Edit2: Can't use -resync for this update. Must delete whole cryptonite data folder and start over.
Edit: New binaries are up and new chain running. Currently at block 90.
Edit2: Can't use -resync for this update. Must delete whole cryptonite data folder and start over.
July 22, 2014, 09:47:14 AM
I believe catia already tried changing it to this but it obviously hasn't worked:
"Cryptonite will download and store a copy of the Cryptonite block chain. A small amount of data will be stored in this directory, and it may grow over time. The wallet will also be stored in this directory."
A "small amount" probably isn't the best phrasing, in the future it might be quite large, but it'll probably take a few years before it even becomes more than a gigabyte in size. Keep in mind I'm only talking about the amount of data required to sync with the network, the longer a node runs the more disk space it will use up. To free up disk space you could just run resync to delete all the old data and start again, but we'll also have a prune/purge command which will delete old blocks without requiring a resync.
"Cryptonite will download and store a copy of the Cryptonite block chain. A small amount of data will be stored in this directory, and it may grow over time. The wallet will also be stored in this directory."
A "small amount" probably isn't the best phrasing, in the future it might be quite large, but it'll probably take a few years before it even becomes more than a gigabyte in size. Keep in mind I'm only talking about the amount of data required to sync with the network, the longer a node runs the more disk space it will use up. To free up disk space you could just run resync to delete all the old data and start again, but we'll also have a prune/purge command which will delete old blocks without requiring a resync.
July 22, 2014, 09:20:28 AM
@catia newest build warns about needing 20gb of free space, I thought this was supposed to be a smaller block chain? yuk yuk yuk.
That's just a warning message left over from Bitcoin. It will be changed.So for the sake of argument, what would you change it to?
July 22, 2014, 01:37:21 AM
@catia newest build warns about needing 20gb of free space, I thought this was supposed to be a smaller block chain? yuk yuk yuk.
That's just a warning message left over from Bitcoin. It will be changed. July 21, 2014, 09:11:13 PM
I was setting it ahead a bit.
New address for spam: cC3hzebkQAAUden219nfzCVjAJRkyZWLq1
New address for spam: cC3hzebkQAAUden219nfzCVjAJRkyZWLq1
damn trouble maker! lol
@catia newest build warns about needing 20gb of free space, I thought this was supposed to be a smaller block chain? yuk yuk yuk.
cNkr2uCukDHEbVAK5JMAnyyoyT5RZtFvaY do your worst
July 21, 2014, 08:31:05 PM
How about #cryptonite on FreeNode ?
I'll try to get you unbanned mrvegad
I'll try to get you unbanned mrvegad
July 21, 2014, 08:05:08 PM
spamming two addresses at 1 sec intervals... devs should I scale that up? or is it enough?
@ mrv damn trouble maker
@ idev thanks bud
you know and irc chan would be nice for this kind of stuff, do you guys have one?
@ mrv damn trouble maker
@ idev thanks bud
you know and irc chan would be nice for this kind of stuff, do you guys have one?
July 21, 2014, 07:46:05 PM
I was setting it ahead a bit.
New address for spam: cC3hzebkQAAUden219nfzCVjAJRkyZWLq1
New address for spam: cC3hzebkQAAUden219nfzCVjAJRkyZWLq1
damn trouble maker! lol
@catia newest build warns about needing 20gb of free space, I thought this was supposed to be a smaller block chain? yuk yuk yuk.
cNkr2uCukDHEbVAK5JMAnyyoyT5RZtFvaY do your worst
July 21, 2014, 07:45:04 PM
Dam! Im banned again 
I was coping old database log files over new ones. That's what probably did it before as well.
I was coping old database log files over new ones. That's what probably did it before as well.
Jump to: