I'll announce it pretty soon
|
|
|
I am still getting the FAILED TO INIT CORE error again
Seems the only way to fix it is to delete the blockchain and wait for it to redownload again.
How do I post the logs?
It's in application folder, the same name exacutable. (qt-boolb.log)
|
|
|
Hey I am getting "Failed to Initialize Core" with the latest version?
Logs ?
|
|
|
BBR is right there in the diagram of the ANN. Looks like star wars episod VII ! The goal of the visualization project was to have an interactive 3D model where people could explore various aspects of SuperNET. Maybe even show the realtime flows of funds and tx. Unfortunately, the dev for it got called away to the real world for a bit, so it is slowed down and might only be a set of graphics for a while James So this is a screen shot of real interactive 3d visualisation ? Zoidberg
|
|
|
BBR is right there in the diagram of the ANN. Looks like star wars episod VII !
|
|
|
btw: does anyone heard some news about James and his SuperNet project ?
|
|
|
Spam seems to be intermittent and is not sustained across all blocks. This isn't the same or similar attack as Monero. Part of me wants to find out what our guy is playing with, but I guess Zoidberg will already have some updates.
Spam has stopped for some time now, but there are some transactions stuck in the pool for some reason. Looks like a script running with mixin count = 4 Stress test for the blockchain I think we need to push per kb fees update soonish. may be some pool payouts with mixins? Clintar, is that you? While we wait for Clintar's feedback, I don't think it is the pool payouts Last 4 large blocks http://chainradar.com/bbr/block/127361http://chainradar.com/bbr/block/127324http://chainradar.com/bbr/block/127290http://chainradar.com/bbr/block/127259All of them have this same 100 BBR payouts with Mixin=4 it use similar inputs of 0.4BBR, that is also weird.... I have strong feeling that it's time to implement fee-per-Kb rule in tx pools.
|
|
|
Spam seems to be intermittent and is not sustained across all blocks. This isn't the same or similar attack as Monero. Part of me wants to find out what our guy is playing with, but I guess Zoidberg will already have some updates.
Spam has stopped for some time now, but there are some transactions stuck in the pool for some reason. Looks like a script running with mixin count = 4 Stress test for the blockchain I think we need to push per kb fees update soonish. may be some pool payouts with mixins? Clintar, is that you?
|
|
|
Any ideas who did that? Zoidberg
|
|
|
It is quiet here.
We could tell an anecdote to each other, to have more fun Or start yet another fight with Monero clan! Zoidberg But, but, I like monero & boolberry punches self in the faceThen we could start another rename/rebrand story! It also activates a lot of trolls
|
|
|
It is quiet here.
We could tell an anecdote to each other, to have more fun Or start yet another fight with Monero clan! Zoidberg
|
|
|
It is quiet here.
We could tell an anecdote to each other, to have more fun
|
|
|
When I send out coin, there are dusts sometimes. How are they determined, where do they go?
Dust outs attached to fee. Finally this all fees joined together and transfered to miner in coinbase (this made to remove dust from uto), but this is soft ruke, default behaviour in wallet. Zoiderg Is the policy of dust same for XMR and BBR? What is the actual rule? The actual rule is that when constructing outputs the amounts smaller than fee is supposed as dust. Also originally was more complicated algo for collecting outputs for new transaction, "select_transfers", that was also manualy included some dust outs into tx, but soon after release i changed this to better and simplier algo. You better to take a look into tx_dust_policy and digit_split_strategy in sources. But may be i got you wront, can you clarify your situation with more details ? (may into pm, or here - up to you) Zoidberg
|
|
|
When I send out coin, there are dusts sometimes. How are they determined, where do they go?
Dust outs attached to fee. Finally this all fees joined together and transfered to miner in coinbase (this made to remove dust from uto), but this is soft ruke, default behaviour in wallet. Zoiderg
|
|
|
#define CURRENCY_DISPLAY_DECIMAL_POINT 12
// COIN - number of smallest units in one coin #define COIN ((uint64_t)100000000) // pow(10, 8)
I found the above code in currency_config.h. Is one coin equal to 10^8 small units? Should the decimal points to be 8 instead of 12? What is the use of the "COIN"? COIN definition actually is not important(and have to be removed in future), it used in couple of unit tests only. What is really important is CURRENCY_DISPLAY_DECIMAL_POINT, this value actually define number of smallest units in one coin (decimal point position). Zoidberg
|
|
|
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. https://bytecoin.org/news.php#news1Do we use reduced memory requirement like BCN? Sure. The goal is the same - to reduce memory usage. Has it been implemented yet? If not, when do you plan to? Memory issue is not critical for BBR yet, due to much shorter blockchain, compared to Bytecoin, atm we focused on GUI usability improvement and working on DB implementation in background. Anyway, i think db will be released close to NY +/- month. Zoidberg
|
|
|
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. https://bytecoin.org/news.php#news1Do we use reduced memory requirement like BCN? Sure. The goal is the same - to reduce memory usage.
|
|
|
Does BBR have different blockchain file for 3 different OS?
Yes. because boost serialization is not portable format, it different under different OS. We shared 2 files - for Linux an for Mac, but usually u don't need it. Zoidberg 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". https://bytecoin.org/news.php#news1Are we going to do similar? No, we going different way. Bytecoin has made some kind of "handmade" storage, instead of use well known database engine, like leveldb. We (with big help of scruffy scruffington) already made version of leveldb which builds with cmake under visual studio / gcc, i believe this way is better - less development risks, clear most of devs who already faced with bitcoin codebase, which also use leveldb. Zoidberg.
|
|
|
Does BBR have different blockchain file for 3 different OS?
Yes. because boost serialization is not portable format, it different under different OS. We shared 2 files - for Linux an for Mac, but usually u don't need it. Zoidberg
|
|
|
|