 Show Posts
|
|
Pages: [1]
|
@OrsonJ and @sowle, congratulation for the release of the technical paper ! My only interrogation would be about the part 3.2, where it is said that hf could be considered random, but the owner somewhat controls f : wouldn't it be possible for him to choose a f that gives him an advantage in the resolution of the inequation 3.2 ? For instance, if f = L, wouldn't hf always be 0 because of the modulo L ?
Thank you too much! This is a very good question! Indeed, if f = L an adversary may stake very easily as L mod L = 0 and thus hf = 0 too. This is why I added f != 0 (mod L) requirement to section 3.3. And there's an easy way to ensure f != 0 for commitments without additional data. I'm going to cover this in the next paper update. I was also wondering, is such scheme compatible with Cold Staking ? I couldn't find any info regarding this security feature on the roadmap, is this something that could be implemented in Zano in the future ?
We at Zano don't favor cold staking much because we believe it creates incentives that favor centralization. |
|
|
|
I would like to understand how you will implement RingCT + PoS, because as far as I know the amount needs to be revealed to check that the 'weight' is indeed correct. I guess that you could include a range proof instead of revealing the exact amount, but it still is a big hint of the real UTXO amount. So how exactly do you plan to resolve this issue ?
Thanks for the question! As OrsonJ said, we'd been working on a technical paper and released it recently: https://github.com/hyle-team/docs/tree/master/PoS/PoS_with_HAI hope it will help to get the idea. Feel free to ask any questions. Any comments, thoughts and feedback are also much appreciated! Here's the link to our reddit post where some valuable comments might also appear: https://www.reddit.com/r/Zano/comments/oz4bol/technical_discussion_a_proofofstake_scheme_for/ |
|
|
|
Hey, everyone! New Boolberry release v0.3.0.91 is here! https://github.com/cryptozoidberg/boolberry/releases/tag/v0.3.0.91GUI: * fixed an issue with wallet's restoration using a seed phrase CLI wallet (simplewallet): * --log-level option added to comply with the same daemon option; * --log-file option added. Now a user can override the log file name, which is simplewallet.log by default. General: * few minor improvements were made for daemon RPC and P2P handshake Boolberry team |
|
|
|
Hey, guys! While Zano mainnet is getting ready we keep improving Boolberry, and quite a few changes were made recently. Here I would like to highlight the most important of them for you: General: * log library was updated to the version which supports log channels (taken from Zano) * added anti-deadlock mechanism, which could track potential traps and save us a lot of time in case of multithreading problems * fixed a bug with possible http flood (thanks to anonimal for pointing to this) * implemented secure and compact Boolberry->Zano coinswap mechanism GUI: * we ported GUI library from old unsupported QT WebKit to stable and smooth QTWebEngine (special thanks to our contributor Alexandra (aldobryn on github) ) * added Unicode support for wallet file path, now it can easily be located in your favorite folder CLI wallet (simplewallet): * simplewallet was greatly improved to be able to work with modern exchanges: ** offline mode implemented for cold wallet support ** exchange API for cold-signing was reviewed and updated ** fixed a bug with incorrect coins handling for watch-only wallets * simplewallet got new commands: ** viewkey -- shows your view keypair ** spendkey -- shows your spend keypair ** recent_blocks -- prints income/outgo per-block summary for last N block containing your txs (it's useful, try it!) ** show_dust -- as you may expect shows how much dust (tiny unspent outputs) you have ** print_ki -- prints key image info * sweep_below command and RPC was improved to work better when lots of small outputs are present in the wallet Today we're releasing a new build: Boolberry 0.3.0.90 containing all these improvements: https://github.com/cryptozoidberg/boolberry/releases/tag/v0.3.0.90Thank you for your support and feedback! Boolberry team |
|
|
|
Please help me. My wallet is in sync but not deposited. Updated the latest wallet  Hi! Thank you for the log file and sorry for the issue. As I can see, a few times you tried to send all the amount you have in one transaction. Namely, you had 923.396 and you put 923.396 as a transaction amount, but this is not possible due to the fee = 0.001, so you can transfer only 923.395. This case is not handled in our GUI wallet, we'll fix it later. Please, take this into account. Also, your wallet has been trying to send incorrect transactions with repeating key images. This is a very unexpected case and it's not clear how it happened, unfortunately. I'd recommend you to do the following: 1. Make a backup (!) of your wallet keys file ( C:\Program Files\Boolberry\thanh.keys in your case ) and copy it to a safe place (usb flash drive, cloud storage etc.) 2. Download and install the latest stable version of Boolberry from https://github.com/cryptozoidberg/boolberry/releases/tag/v0.3.0.863. Remove or rename old log file ( C:\Users\_YOUR_USER_\AppData\Roaming\Boolb\Boolberry.log ) 4. Remove your wallet data file ( C:\Program Files\Boolberry\thanh, but DO NOT remove keys file: C:\Program Files\Boolberry\thanh.keys ) 5. Launch Boolberry with --log-level=2 option. You can either edit shortcut properties:  Or launch Command Prompt, navigate to Boolberry directory and type Boolberry.exe --log-level=2 6. Open your wallet. "Synchronizing wallet..." should appear for a few minutes. Wait until it's synchronized. 7. Try to send coins. Start with small amounts (10..50 in your case), if okay proceed to bigger. If this does not help, please send a new log file ( C:\Users\_YOUR_USER_\AppData\Roaming\Boolb\Boolberry.log ) to me or CZ via direct messages for further investigation. Sorry for the inconvenience! I hope wallet resynchronization with the recent BBR build will resolve the issue. |
|
|
|
okay I narrowed down to one error.... "could not find boost_atomic"
...using boost 1.54, as recommended
Hi, tybiboune! I'm using Boost 1.66 now on Ubuntu 17.10 with gcc 7.2.0 and Boolberry builds quite well with it. If you didn't solve the issue, I suggest you building Boost 1.66 from sources. Here's how it can be done: wget https://dl.bintray.com/boostorg/release/1.66.0/source/boost_1_66_0.tar.gz
tar -xvf boost_1_66_0.tar.gz
cd ~/boost_1_66_0
./bootstrap.sh --with-libraries=system,filesystem,thread,date_time,chrono,regex,serialization,atomic,program_options,locale
./b2
If everything is okay then “The Boost C++ Libraries were successfully built!” message will appear. Then you need to set BOOST_ROOT environment variable to reflect correct Boost path. For example, you may put this line to your ~/.bashrc file: export BOOST_ROOT=/home/user/boost_1_66_0 Make sure it was actually set: user@ubuntu:~/boost_1_66_0$ env | grep boost
BOOST_ROOT=/home/user/boost_1_66_0
After that, cmake hopefully will run with no issues. |
|
|
|
Clint the LMDB version seems to take more time to synchronize with the old version. My took about two days and got stuck in the middle.
What version of Boolberry are you running? Did you try using --db-sync-mode command-line option to speed-up synchronization as I suggested above? |
|
|
|
Yes windows 8.1 I'm using. I did try --db-sync-mode=fast on the shortcut before and didn't notice much difference. But I'm trying it again and letting it run overnight to see if there is a difference long term. Thanks  On block 138,000 right now after ~48 hrs. I've just tried to sync from scratch with --db-sync-mode=fast on my i3-6320 with 5400 rpm Western Digital HDD. Windows 7 x64 with Booberry v0.3.0.68. After an hour I'm at height 130800 (~9-12 hours to get fully synced). |
|
|
|
I have a Mac, soon the Bittrex wallet will be closed, and all XBB coins will disappear. It's funny, huh?
Bittrex delisted XBB almost a year ago. If you still have some XBB there just withdraw them to your local wallet. |
|
|
|
Thx.. but the problem is I'm using this computer. But it seems much slower with the latest version. If your computer doesn't have an SSD and only has a rotating HDD, using --db-sync-mode=fast should increase synchronization speed also. Just make sure you have Boolberry v0.3.0.68 and use this CLI option. I tried it on the qt. but didn't work. Where do I put that command --db-sync-mode=fast ? thx Ok, I see. Which OS do you use? There's a couple of options on Windows. You can create a shortcut to Boolberry.exe then right click it, go to Properties/Shortcut and change Target from this: C:\YOUR_BBR_FOLDER\Boolberry.exe to this: C:\YOUR_BBR_FOLDER\Boolberry.exe --db-sync-mode=fast Then use this shortcut to start Boolberry. Alternatively, you can open the Command Prompt, navigate to Boolberry folder and type: Boolberry.exe --db-sync-mode=fast |
|
|
|
Thx.. but the problem is I'm using this computer. But it seems much slower with the latest version. If your computer doesn't have an SSD and only has a rotating HDD, using --db-sync-mode=fast should increase synchronization speed also. Just make sure you have Boolberry v0.3.0.68 and use this CLI option. |
|
|
|
Anyone have an updated chainstate for the new wallet so I can bootstrap it plz? EDIT:Because at this rate...it will take 1 1/2 weeks left open 24/7 to sync.  To speed up the synchronization process you may want to move Boolberry blockchain to SSD drive and/or use --db-sync-mode=fast daemon CLI option. Please, make sure you're using v0.3.0.68. Once the blockchain is fully synced it's recommended to remove --db-sync-mode=fast or to switch to --db-sync-mode=safe (default) to avoid DB issues in a case of power fails or OS crash. In the next release (v0.3.0.69 I guess) --db-sync-mode=ultra will also be available for even faster synchronization for a price of consuming some RAM. |
|
|
|
replaced wallets on bbRA ****************** without Payment Id
These are integrated addresses we implemented in May/June. It's a combination of standard address and payment id in one encoded string for convenience. simplewallet now has a new command "integrated_address" to perform a conversion both ways and can seamlessly send coins to both type of addresses as well as gui wallet. Until pools upgrade their daemons/wallets up to the last version, you may withdraw first to your wallet, then transfer to the exchange. Please make sure you have the latest version. |
|
|
|
it did show the correct public address, and it refresh the wallet scanning the whole blockchain
but it show 0 available coins
Hi, mitzi101. Thank you for reporting the issue! I confirm that atm restoring a wallet from a seed phrase will limit the blockchain scan window and as a consequence may end up with showing zero balance. All your coins are safe, so don't worry. They just don't show up due to the bug. This one will be fixed asap, I guess. I opened an issue on GitHub so you can track the status: https://github.com/cryptozoidberg/boolberry/issues/78 |
|
|
|
I solved also the sync problem with first use a demon what no have the "check the security bug" and past block 780000. Then use a newer demon what check the security bug.
Good solution!! I don't see much good nodes in connection list either. |
|
|
|
Thank you, buddy, jut one little question: why you acquire m_blockchain_lock (it's already owned by this code at the beginning of function)?
my fault) fixed |
|
|
|
What i can do now for sync the blockhain?
Without syncing no transaction is possible, because simplewallet say the demon are busy.
You should wait for fixed binaries from zoidbeg. My fix seem to solve the issue (my build synced from the scratch normally) so I hope zoidbeg will accept it very soon. Or you can get somewhere blockchain.bin past 750k block — your current daemon will work because it will sync past the critical point |
|
|
|
As to invalid txs with invalid key_images. There are 7 in the blockchain. Thanks to zoidberg's fix it's completely fixed now. Invalid txs: Invalid key image: <26e8958fc2b227b045c3f489f2ef98f0d5dfac05d3c63339b13802886d53fc05>, amount: 0.990000000000, tx: <9f395234de50d836337dacef0133031f34d7ccf77ff261fdd710494675383e69>
Invalid key image: <c7176a703d4dd84fba3c0b760d10670f2a2053fa2c39ccc64ec7fd7792ac037a>, amount: 0.990000000000, tx: <ff43d5b09e49d619a14ea243ebc2640a187813b2afd67f1090da948204b949c2>
Invalid key image: <26e8958fc2b227b045c3f489f2ef98f0d5dfac05d3c63339b13802886d53fc85>, amount: 899.980000000000, tx: <d2a66d7dc40b8a618d15f878c9153a61d0a87dde703df8185f41b0c6078d0a56>
Invalid key image: <0000000000000000000000000000000000000000000000000000000000000000>, amount: 899.980000000000, tx: <6130a0cbc7a19ba662d7bef35cd07bb948045e5d942d8db699748d781b2a73a4>
Invalid key image: <0000000000000000000000000000000000000000000000000000000000000080>, amount: 1799.990000000000, tx: <9584905ab31a2cda1ee2def9a853b02103cd66af67c9c525762e031ed7fa8d96>
Invalid key image: <c7176a703d4dd84fba3c0b760d10670f2a2053fa2c39ccc64ec7fd7792ac03fa>, amount: 1799.990000000000, tx: <8b02b0477493f6d86c7f9067ada619bb877faedc7d4312f3947ff8b67cc4422b>
Invalid key image: <ecffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff7f>, amount: 1799.990000000000, tx: <38999f6326860e4f48543c978a3f79e135d8ff0e7ce2ad5f5f169d455ecbcd6e>
Invalid txs with relation to blocks and timestamps: tx amount block timestamp
9f395234de50d836337dacef0133031f34d7ccf77ff261fdd710494675383e69 0.99 757131 2017-04-10 22:54:06
ff43d5b09e49d619a14ea243ebc2640a187813b2afd67f1090da948204b949c2 0.99 757134 2017-04-10 22:58:09
d2a66d7dc40b8a618d15f878c9153a61d0a87dde703df8185f41b0c6078d0a56 899.98 757183 2017-04-11 00:03:48
6130a0cbc7a19ba662d7bef35cd07bb948045e5d942d8db699748d781b2a73a4 899.98 757190 2017-04-11 00:14:17
9584905ab31a2cda1ee2def9a853b02103cd66af67c9c525762e031ed7fa8d96 1799.99 757235 2017-04-11 01:05:33
8b02b0477493f6d86c7f9067ada619bb877faedc7d4312f3947ff8b67cc4422b 1799.99 757237 2017-04-11 01:10:58
38999f6326860e4f48543c978a3f79e135d8ff0e7ce2ad5f5f169d455ecbcd6e 1799.99 757241 2017-04-11 01:13:46 As you can see, an attacker tried with small amount tx, then went further. It was performed in ~2 hours at April 11th midnight. |
|
|
|
I can not sync BBR Blockchain.
At Block 757131 get a "Block recognized as orphaned and rejected" message.
And this for hours.
i use a seed node 5.9.44.154:10101
Got the same issue. I found out there are txs with invalid key_image in the blockchain. The first one is at block 757131. On May 9th zoidberg commited a security fix from monero ( https://getmonero.org/2017/05/17/disclosure-of-a-major-bug-in-cryptonote-based-currencies.html) and now each input is being checked against invalid key_image. That's good. Unfortunately, by the time he commited the fix there had already been malformed txs in the blockchain. That's why blockchain can't be resyncronized from the beginning now. I send a pull request to address this issue: https://github.com/cryptozoidberg/boolberry/pull/54 |
|
|
|
|
