.... Did a very basic test. Worked to receive money from my real wallet and send it back.
Suggestion:
If you enter an address that isn't a valid BBR address, it says "wrong address". It would be more informative if it said "invalid address".
Corrected, thank you!
|
|
|
It's syncronizing. I'm not a mac guy, but we have one in my office. I'll let you know how it goes. What should I be testing, btw? Edit: I created a wallet and sent money to it and sent from it. Great! Thank you!
|
|
|
Newbie question... if I pay a higher fee, will this speed up the transaction/ confirmations?
At this moment it's not reasonable. Since transaction flow is pretty low your transactions gonna fit to blocks asap.
|
|
|
Dear friends!
As you may know, last days i was chained to work on pool/cpuminer, but now after all i'm glad to get back to work on BBR, since working with BBR code is a pleasure for me. I want to announce fresh Boolberry version (v0.2.0.26(fa40960)), here is some of the fixed issues:
...
Only after 2 month launch, Boolberry make a huge progress. I´m excited! Thank you Zoidberg and all other supporters. Yes, it happened because i had to interact my BBR work to implement cpuminer/stratum pool. With all bug fix it took almost 3 weeks of my time.... but now it's okay, i'm back to BBR. Zoidberg
|
|
|
Dear friends! As you may know, last days i was chained to work on pool/cpuminer, but now after all i'm glad to get back to work on BBR, since working with BBR code is a pleasure for me. I want to announce fresh Boolberry version (v0.2.0.26(fa40960)), here is some of the fixed issues: * added alias support (now, you can send transactions using @name) * added suggestions to address field, now after you pressed @ and then first letter one the alias name you get suggestions list, based on currently registered aliases: * Now, when you press Generate New Wallet - it opens by default user home directory, and automatically suggest username_wallet.bbr as default wallet name. * After you once saved/opened/generated wallet it memorize last used folder and next open/generate will be oppened in this folder * By default Boolberry wallet now have extension *.bbr + *.bbr.keys, you still able to open old-named files by chosing another filter in Open file dialog (*.* All files). * Fixed issue with big negative number at starting synchronization. What next ? * Storing and displaing recent transfers in wallet * Installer for windows * Add SEH handler to catch crush reports * Prepare yet another presentsation PS: I was talked with Bittrex, they said that they "more than happy" to give Boolberry little more time, and also they asked to traders to leave feedback about Bittrex, and probably explain why do they prefer Polo. I'm also would be very thankful for everyone who will support BBR on Bittrex. PPS: BBR really need MacOS developer to create distrubution package. I have 5 people who got to work and then just gave up, each with different explanations. Wtf ? Is there anyone who can do that ?
|
|
|
Monero devs already made those improvements. See the below quote. It refers to a well known privacy issue on CN coins. We've had a fix for this in the development for weeks now after corresponding with a Bitcoin core devs that should be more effective than the solution for Boolberry, we're just waiting until the core of the software is more mature before we roll it out. Just curious, can you(or someone) point me where exactly in sources did they fix it ? May be i miss something, but as i konw they have the same core as bytecoin and didn't made a hardfork yet. See last few replies -- celestio misspoke. Ok. So, you going to make hard-fork in XMR to fix this ?
|
|
|
Monero devs already made those improvements. See the below quote. It refers to a well known privacy issue on CN coins. We've had a fix for this in the development for weeks now after corresponding with a Bitcoin core devs that should be more effective than the solution for Boolberry, we're just waiting until the core of the software is more mature before we roll it out. Just curious, can you(or someone) point me where exactly in sources did they fix it ? May be i miss something, but as i konw they have the same core as bytecoin and didn't made a hardfork yet. Zoidberg
|
|
|
Nice presentation. Is that why when I try to send with a high number of mixins it won't let me? In that case, do I just keep retrying until there are a lot of mixins? Or maybe I don't get it.
No. When you try to send with big amount of mixin's your transaction is bigger than allowed. This feature is implemented in core, but not enabled in wallet yet, since we need to figure out how to represent this feature in GUI and make it clear.
|
|
|
Good News Everybody!
We are proud to announce that we're starting a series of presentations in which we'll explain Boolberry's unique and very important features.
We've created an easy-to-understand presentation that explains how Boolberry solves CryptoNote flaws.
In this first presentation, you'll find out how Boolberry provides guaranteed privacy, while other CryptoNote coins cannot.> Download .pdf
Discussion thread: https://bitcointalk.org/index.php?topic=697355.0
|
|
|
HI Crypto,
Any idea why my windows wallet crashes every day on average ??
Trippy
Hi TrippyPippy! Can you list a steps to reproduce it ? What windows version ? What GUI version ? How much memory do you have ? Also would be nice to get logs from your GUI (qt-boolb.log). I want to help, but i need more info to figure out what happend. Zoidberg Hi Crypto, I leave it running all the time but at random points throughout the day it crashes with a windows message and I have to restart it. Windows 2008 R2 Gui 0.2.0.24(1ada156) Ram 2GB Partial Log: 2014-Jul-15 13:28:00.354222 [P2P1]Connect failed to 125.16.13.10:10101 2014-Jul-15 13:28:00.355199 [P2P1]Connecting to 118.219.85.174:10101(white=0, last_seen: d0.h11.m31.s24)... 2014-Jul-15 13:28:05.355391 [P2P1]Connect failed to 118.219.85.174:10101 ...... Thank you for feedback. The first guess is that there is not enought RAM for running it. I'll add crush handler for windows version will research this dumps, according to current tasks i think it will take about two days.
|
|
|
HI Crypto,
Any idea why my windows wallet crashes every day on average ??
Trippy
Hi TrippyPippy! Can you list a steps to reproduce it ? What windows version ? What GUI version ? How much memory do you have ? Also would be nice to get logs from your GUI (qt-boolb.log). I want to help, but i need more info to figure out what happend. Zoidberg
|
|
|
parsing algo: wildkeccak [2014-07-15 11:18:39] wildkeccak scratchpad cache /root/.cache/boolberry/scratchpad.bin [2014-07-15 11:18:39] Using JSON-RPC 2.0 [2014-07-15 11:18:39] hugetlb not available [2014-07-15 11:18:39] scratchpad allocation failed
cpu-muiti,any one can help me..
What OS ? What hardware (physical memory size) ? ubuntu 12.04 memory is virtual 1 GB git pull & make
|
|
|
parsing algo: wildkeccak [2014-07-15 11:18:39] wildkeccak scratchpad cache /root/.cache/boolberry/scratchpad.bin [2014-07-15 11:18:39] Using JSON-RPC 2.0 [2014-07-15 11:18:39] hugetlb not available [2014-07-15 11:18:39] scratchpad allocation failed
cpu-muiti,any one can help me..
What OS ? What hardware (physical memory size) ?
|
|
|
I actually think BBR has a bigger upside than XMR.
As a trader, I've done 100s of transfers in at least 7-8 CN coins... And I absolutely dread transferring XMR to and from exchanges (what fun).
But it's a pleasure to use that cool little BBR wallet... It's not just the GUI, but the BBR network seems to run smoother and faster and reliably.
Thank you! And, at this moment we preparing presentation about why BBR is so fast and what actually mean's BBR's features. Because, as i figured out, text that we currently have on website is totally unclear for most people.
|
|
|
i made a TX to poloniex and it basically disappeared:
it's in the log, can't find the txid in the block chain
Perhaps if there was a way to resync the whole block chain? but i cannot find datafiles in the dir, any ideas how i can do this?
edit: looks like deleting wallet.bin did it. Resync'd using the keys file
1. Which version of daemon/wallet/GUI are you using ? (for CLI start with --version perameter) 2. Turn off daemon, remove C:\Users\UserName\AppData\Roaming\boolb\poolstate.bin 3. Try again. NVM first attempt (wallet.bin) did not work, however what you suggested above (rm poolstate.bin) worked. Thanks. Hey, what version have u used?? If this is a fresh version i need your logs to figure out the problem and fix it.
|
|
|
i made a TX to poloniex and it basically disappeared:
it's in the log, can't find the txid in the block chain
Perhaps if there was a way to resync the whole block chain? but i cannot find datafiles in the dir, any ideas how i can do this?
edit: looks like deleting wallet.bin did it. Resync'd using the keys file
1. Which version of daemon/wallet/GUI are you using ? (for CLI start with --version perameter) 2. Turn off daemon, remove C:\Users\UserName\AppData\Roaming\boolb\poolstate.bin 3. Try again.
|
|
|
zoidberg, you'll want to call pthread_mutex_init(&applog_lock, NULL ); before you're reading the scratchpad via HTTP requests and making applog() calls...
It will crash pthreads on Windows if applog_lock remains uninitialized. The mingw Windows builds may be more forgiving, but my Visual Studio build isn't...
Christian
Thank you, fixed & pushed!
|
|
|
- Transaction outs with guaranteed anonymity. An additional attribute for out is added: it can ONLY be used in the transaction with mixin level in ring signature not less than a given number. The feature is added to ensure the user's anonymity of transactions ring signature over time.
I might be missing something, but wouldn't it be more effective to enforce the mixin level on a more global level? Mixing in a key which appears somewhere else in an unmixed fashion will be less effective against smart blockchain analysis, after all. For my point it is better to leave possibilty to have two subset of transactions outs - outs with guaranteed anonymity and regular outs, and different outs types could transform to each other during the circulation. Actually unlinkability is e feature that not need to everyone, enforcing this feature for every transaction will blow up blockchain with ringsignatures. So i've made this feature optional, but i believe still secure.
|
|
|
|