[BCN] Bytecoin. Secure, private, untraceable since 2012

[matej krkic]

Its been a good week for Bytecoin. We made it to top 10, we got our website, and last but not least, we got these updates!

Time to celebrate?

I agree, its been a nice week.
I think im gonna open a bottle of champagne.

Champagne! So classy! Meanwhile i got beer.

+1
One more beer for bytecoin!

[1713556905]

1713556905

[1713556905]

1713556905

[1713556905]

1713556905

[1713556905]

1713556905

[sgk]

Major Bytecoin update

Bytecoin source code has been largely updated.

1) The block chain has been moved out of RAM, which cut down the usage from 4 GB to 850 MB. In the next releases it is expected to become as low as 350 MB.
2) The block chain file is now unified across all platforms.

When you run the new binaries, the daemon will automatically convert your old block chain to the new format. Your "blockchain.bin" file will be split into 3 files: "blockindexes.dat", "blockscache.dat", "blocks.dat".

Next week there will be another significant update!

P.S. BCN devs would like to thank all the beta tester from the community that helped them launch this release.

https://bytecoin.org/news.php#news1

[babybonobo]

Cheers!  I used the beta and it seems to be working ok...converted the blockchain over

[smooth]

Major Bytecoin update

Bytecoin source code has been largely updated.

1) The block chain has been moved out of RAM, which cut down the usage from 4 GB to 850 MB. In the next releases it is expected to become as low as 350 MB.
2) The block chain file is now unified across all platforms.

When you run the new binaries, the daemon will automatically convert your old block chain to the new format. Your "blockchain.bin" file will be split into 3 files: "blockindexes.dat", "blockscache.dat", "blocks.dat".

Next week there will be another significant update!

P.S. BCN devs would like to thank all the beta tester from the community that helped them launch this release.

https://bytecoin.org/news.php#news1

Would we be able to find out how much the low memory load will effect it compared to before and why not done this way in the first place?

I browsed the code briefly and it seems to be doing some kind of caching, so the performance should not be affected too badly on the assumptions that: 1) you leave your node running, and 2) most of the block chain is not used, so the portion that is used can still fit in the smaller RAM usage.

As for why it wasn't done in the first place, it is slightly more complex and required more code (and testing, etc.). The blockchain-in-RAM approach works just fine as long as the blockchain is small enough, which is the case for every new coin. Only when it gets bigger is something more needed. So the developer or developers probably just deferred it until needed, and then implemented it. Totally reasonable.

[JazzCouncil]

Major Bytecoin update

Bytecoin source code has been largely updated.

1) The block chain has been moved out of RAM, which cut down the usage from 4 GB to 850 MB. In the next releases it is expected to become as low as 350 MB.
2) The block chain file is now unified across all platforms.

When you run the new binaries, the daemon will automatically convert your old block chain to the new format. Your "blockchain.bin" file will be split into 3 files: "blockindexes.dat", "blockscache.dat", "blocks.dat".

Next week there will be another significant update!

P.S. BCN devs would like to thank all the beta tester from the community that helped them launch this release.

https://bytecoin.org/news.php#news1

Definitive proof that our devs might be the ones of a very few people in cryptoworld who really understand the technology and are willing to bring it to the whole new level.

[UnitedColors]

Definitive proof that our devs might be the ones of a very few people in cryptoworld who really understand the technology and are willing to bring it to the whole new level.

Devs never disappoint. Im so proud to be a part of this community.

[freshprince]

Major Bytecoin update

Bytecoin source code has been largely updated.

1) The block chain has been moved out of RAM, which cut down the usage from 4 GB to 850 MB. In the next releases it is expected to become as low as 350 MB.
2) The block chain file is now unified across all platforms.

When you run the new binaries, the daemon will automatically convert your old block chain to the new format. Your "blockchain.bin" file will be split into 3 files: "blockindexes.dat", "blockscache.dat", "blocks.dat".

Next week there will be another significant update!

P.S. BCN devs would like to thank all the beta tester from the community that helped them launch this release.

https://bytecoin.org/news.php#news1

GREAT UPDATE.

Now looking forvard to the next updates!

[JJKirsch]

Definitive proof that our devs might be the ones of a very few people in cryptoworld who really understand the technology and are willing to bring it to the whole new level.

Indeed. Should be more complicated than creating damn forks huh?

[AtomicDoge]

Devs never disappoint. Im so proud to be a part of this community.

Me too. We get really cool updates here.

[Emily Dickinson]

 ;)Nice go the the moon

[dragonmike]

Is it even worth mining this with a single core2duo? :-/

[yvg1900]

New M7u version of yam miner is available. Major addition in this release is support for many new coins - DVK,MYR,BCN,QCN,FCN and XMR.

yam M7u supports FantomCoin CryptoNight merged mining of FCN-XMR, FCN-BCN and FCN-QCN - check readme.txt and default config for details.

yam M7u has special algorithm variation for faster CryptoNight mining on AMD CPUs, resulting in 360+ H/s on AMD FX-8320 at stock freqs.

Primary download location for yam M7u is https://t.co/whkQyh2XA2
Alternative download location for yam M7u is http://t.co/A9c5GryPBy
Chinese users may donwload yam M7u at http://t.co/qsWEtQEMhZ

Enjoy.

[slb]

Major Bytecoin update

Bytecoin source code has been largely updated.

1) The block chain has been moved out of RAM, which cut down the usage from 4 GB to 850 MB. In the next releases it is expected to become as low as 350 MB.
2) The block chain file is now unified across all platforms.

When you run the new binaries, the daemon will automatically convert your old block chain to the new format. Your "blockchain.bin" file will be split into 3 files: "blockindexes.dat", "blockscache.dat", "blocks.dat".

Next week there will be another significant update!

P.S. BCN devs would like to thank all the beta tester from the community that helped them launch this release.

https://bytecoin.org/news.php#news1

There is a huge bug in this release. Only users with downloaded blockchain can use is. Users with no downloaded blockchain will receive an error and daemon will not start.

If you are a new user follow the following steps to get a working wallet:
1. Download binaries
2. Create .bytecoin folder in the appropriate folder
3. Download the block chain into the .bytecoin folder
4. Start bytecoind
5. Start simplewallet

Enjoy
21YR5mw5BF2ah3yVE3kbhkjDwvuv21VR6D7hnpm4zHveDsvq5WEwyTxXLXNwtU5K4Pen89ZZzJ81fB3 vxHABEUJCAhxXz2v

[brander]

Code:

2014-Jun-21 14:50:03.393823 [P2P9][71.126.167.33:8080 OUT]Sync data returned unk
nown top block: 504000 -> 507051 [3051 blocks (4 days) behind]
SYNCHRONIZATION started
2014-Jun-21 14:50:08.773830 [P2P5][162.210.192.66:8090 OUT]Sync data returned un
known top block: 504000 -> 507051 [3051 blocks (4 days) behind]
SYNCHRONIZATION started
2014-Jun-21 14:50:09.193831 [P2P2][78.192.77.48:8080 OUT]Sync data returned unkn
own top block: 504000 -> 507051 [3051 blocks (4 days) behind]
SYNCHRONIZATION started
2014-Jun-21 14:50:17.643843 [P2P2][27.254.65.161:8080 OUT]Sync data returned unk
nown top block: 504004 -> 507051 [3047 blocks (4 days) behind]
SYNCHRONIZATION started
2014-Jun-21 14:50:43.373879 [P2P5]ERROR c:\projects\sorrybigbro\contrib\epee\inc
lude\net\levin_protocol_handler_async.h:644 Failed to do_send()
2014-Jun-21 14:50:43.673879 [P2P5]ERROR c:\projects\sorrybigbro\contrib\epee\inc
lude\net\levin_protocol_handler_async.h:644 Failed to do_send()
2014-Jun-21 14:50:44.643880 [P2P2][61.90.204.246:8080 OUT]Sync data returned unk
nown top block: 504117 -> 507051 [2934 blocks (4 days) behind]
SYNCHRONIZATION started
2014-Jun-21 14:50:45.633882 [P2P5]ERROR c:\projects\sorrybigbro\contrib\epee\inc
lude\net\levin_protocol_handler_async.h:644 Failed to do_send()
2014-Jun-21 14:50:46.673883 [P2P5]ERROR c:\projects\sorrybigbro\contrib\epee\inc
lude\net\levin_protocol_handler_async.h:644 Failed to do_send()
2014-Jun-21 14:50:48.953886 [P2P5]ERROR c:\projects\sorrybigbro\contrib\epee\inc
lude\net\levin_protocol_handler_async.h:644 Failed to do_send()
2014-Jun-21 14:50:49.533887 [P2P5]ERROR c:\projects\sorrybigbro\contrib\epee\inc
lude\net\levin_protocol_handler_async.h:644 Failed to do_send()
2014-Jun-21 14:51:05.823910 [P2P1][37.193.68.157:8080 OUT]Sync data returned unk
nown top block: 504254 -> 507051 [2797 blocks (3 days) behind]
SYNCHRONIZATION started
2014-Jun-21 14:51:13.113920 [P2P7]ERROR c:\projects\sorrybigbro\contrib\epee\inc
lude\net\levin_protocol_handler_async.h:644 Failed to do_send()
2014-Jun-21 14:51:19.673929 [P2P2][sock 796] Some problems at write: An existing
 connection was forcibly closed by the remote host:10054
2014-Jun-21 14:51:19.823930 [P2P1][188.24.158.106:8080 OUT]Sync data returned un
known top block: 504355 -> 507051 [2696 blocks (3 days) behind]
SYNCHRONIZATION started
2014-Jun-21 14:51:24.303936 [P2P2]
**********************************************************************
You are now synchronized with the network. You may now start simplewallet.

Please note, that the blockchain will be saved only after you quit the daemon wi
th "exit" command or if you use "save" command.
Otherwise, you will possibly need to synchronize the blockchain again.

Use "help" command to see the list of available commands.
**********************************************************************

Nice to see some development. Dunno if this is normal but i am getting the above errors.

Greetings

[Rytir_fik]

Code:

2014-Jun-21 14:50:03.393823 [P2P9][71.126.167.33:8080 OUT]Sync data returned unk
nown top block: 504000 -> 507051 [3051 blocks (4 days) behind]
SYNCHRONIZATION started
2014-Jun-21 14:50:08.773830 [P2P5][162.210.192.66:8090 OUT]Sync data returned un
known top block: 504000 -> 507051 [3051 blocks (4 days) behind]
SYNCHRONIZATION started
2014-Jun-21 14:50:09.193831 [P2P2][78.192.77.48:8080 OUT]Sync data returned unkn
own top block: 504000 -> 507051 [3051 blocks (4 days) behind]
SYNCHRONIZATION started
2014-Jun-21 14:50:17.643843 [P2P2][27.254.65.161:8080 OUT]Sync data returned unk
nown top block: 504004 -> 507051 [3047 blocks (4 days) behind]
SYNCHRONIZATION started
2014-Jun-21 14:50:43.373879 [P2P5]ERROR c:\projects\sorrybigbro\contrib\epee\inc
lude\net\levin_protocol_handler_async.h:644 Failed to do_send()
2014-Jun-21 14:50:43.673879 [P2P5]ERROR c:\projects\sorrybigbro\contrib\epee\inc
lude\net\levin_protocol_handler_async.h:644 Failed to do_send()
2014-Jun-21 14:50:44.643880 [P2P2][61.90.204.246:8080 OUT]Sync data returned unk
nown top block: 504117 -> 507051 [2934 blocks (4 days) behind]
SYNCHRONIZATION started
2014-Jun-21 14:50:45.633882 [P2P5]ERROR c:\projects\sorrybigbro\contrib\epee\inc
lude\net\levin_protocol_handler_async.h:644 Failed to do_send()
2014-Jun-21 14:50:46.673883 [P2P5]ERROR c:\projects\sorrybigbro\contrib\epee\inc
lude\net\levin_protocol_handler_async.h:644 Failed to do_send()
2014-Jun-21 14:50:48.953886 [P2P5]ERROR c:\projects\sorrybigbro\contrib\epee\inc
lude\net\levin_protocol_handler_async.h:644 Failed to do_send()
2014-Jun-21 14:50:49.533887 [P2P5]ERROR c:\projects\sorrybigbro\contrib\epee\inc
lude\net\levin_protocol_handler_async.h:644 Failed to do_send()
2014-Jun-21 14:51:05.823910 [P2P1][37.193.68.157:8080 OUT]Sync data returned unk
nown top block: 504254 -> 507051 [2797 blocks (3 days) behind]
SYNCHRONIZATION started
2014-Jun-21 14:51:13.113920 [P2P7]ERROR c:\projects\sorrybigbro\contrib\epee\inc
lude\net\levin_protocol_handler_async.h:644 Failed to do_send()
2014-Jun-21 14:51:19.673929 [P2P2][sock 796] Some problems at write: An existing
 connection was forcibly closed by the remote host:10054
2014-Jun-21 14:51:19.823930 [P2P1][188.24.158.106:8080 OUT]Sync data returned un
known top block: 504355 -> 507051 [2696 blocks (3 days) behind]
SYNCHRONIZATION started
2014-Jun-21 14:51:24.303936 [P2P2]
**********************************************************************
You are now synchronized with the network. You may now start simplewallet.

Please note, that the blockchain will be saved only after you quit the daemon wi
th "exit" command or if you use "save" command.
Otherwise, you will possibly need to synchronize the blockchain again.

Use "help" command to see the list of available commands.
**********************************************************************

Nice to see some development. Dunno if this is normal but i am getting the above errors.

Greetings

I have asked during betatesting on this bigbrother errors because I got a lot of red rows with it. Dev people told me that It's another problem, which currently takes place in all CryptoNote coins not only bytecoin and the most important is that this does not have impact on the deamon functions. They are going to fix the problem soon but it is not probably priority nr.1 because it does not harm the function .... It makes sense to me.

[AtomicDoge]

Major Bytecoin update

Bytecoin source code has been largely updated.

1) The block chain has been moved out of RAM, which cut down the usage from 4 GB to 850 MB. In the next releases it is expected to become as low as 350 MB.
2) The block chain file is now unified across all platforms.

When you run the new binaries, the daemon will automatically convert your old block chain to the new format. Your "blockchain.bin" file will be split into 3 files: "blockindexes.dat", "blockscache.dat", "blocks.dat".

Next week there will be another significant update!

P.S. BCN devs would like to thank all the beta tester from the community that helped them launch this release.

https://bytecoin.org/news.php#news1

There is a huge bug in this release. Only users with downloaded blockchain can use is. Users with no downloaded blockchain will receive an error and daemon will not start.

If you are a new user follow the following steps to get a working wallet:
1. Download binaries
2. Create .bytecoin folder in the appropriate folder
3. Download the block chain into the .bytecoin folder
4. Start bytecoind
5. Start simplewallet

Enjoy
21YR5mw5BF2ah3yVE3kbhkjDwvuv21VR6D7hnpm4zHveDsvq5WEwyTxXLXNwtU5K4Pen89ZZzJ81fB3 vxHABEUJCAhxXz2v

Nobody ever cares about new people 
At least im glad this bug is easily fixable.

[Rias]

There is a huge bug in this release. Only users with downloaded blockchain can use is. Users with no downloaded blockchain will receive an error and daemon will not start.

If you are a new user follow the following steps to get a working wallet:
1. Download binaries
2. Create .bytecoin folder in the appropriate folder
3. Download the block chain into the .bytecoin folder
4. Start bytecoind
5. Start simplewallet

Enjoy
21YR5mw5BF2ah3yVE3kbhkjDwvuv21VR6D7hnpm4zHveDsvq5WEwyTxXLXNwtU5K4Pen89ZZzJ81fB3 vxHABEUJCAhxXz2v

Nobody ever cares about new people 
At least im glad this bug is easily fixable.

It's actually done in just 1 step. Just create the .bytecoin folder:

C:/Users/%Username%/AppData/Roaming/bytecoin - Windows
~/.bytecoin - Linux and Mac.

[JazzCouncil]

Nobody ever cares about new people 
At least im glad this bug is easily fixable.

No. Don't even try to complain about that.  In the process of development it is really hard to observe all possible errors.
All technologies can have bugs found in them.

[AtomicDoge]

It's actually done in just 1 step. Just create the .bytecoin folder:
C:/Users/%Username%/AppData/Roaming/bytecoin - Windows
~/.bytecoin - Linux and Mac.

Even better! Thanks!

No. Don't even try to complain about that.  In the process of development it is really hard to observe all possible errors.
All technologies can have bugs found in them.

I didnt mean to complain. I think our developers do a great job and that bug is not even a deal, as said before, it can be fixed in 1 step.

[slb]

It's actually done in just 1 step. Just create the .bytecoin folder:

C:/Users/%Username%/AppData/Roaming/bytecoin - Windows
~/.bytecoin - Linux and Mac.

Cool Thanks for correcting.