Looks like BBR network is under attack, all pools down(not accepting shares)
Yikes. Don't know what happened there. Restarted daemon and now https://cncoin.farm is going again |
|
|
|
If you are just going by those blockchain explorers, the discussion lately has been that they seem to be relying on each other for their info and have been lagging behind for some reason lately. Seems like poloniex may be using them for their blockchain info, too, as I had transactions not showing up until those two caught up, too. Someone contacted one of those and they said they should be fine now, though, unless it's just happening again. Or maybe you didn't see them show up in your own wallet? It should only take 6 confirmations for funds to be usable I think, so more like 14 minutes I think is normal? |
|
|
|
Those stats haven't been working for some time. They were informative but I don't think many people ever looked at them. I used the stats page mainly to see what aliases were available. I'm very busy with my main occupation but I might have time in the next few days to recreate and host them on a crypto related website I'm setting up if you don't get a response from Crypto Zoidberg. He is the person in control of the boolberry.com website. I whipped something up based on what was on boolberry.com. It's at https://cncoin.farm/munin/ if you want to use it. Click on the BoolberryStats link to see graphs. Thank You! I feel bad for not getting something put up. But honestly, I had some issues. I've never used Munin and ran into some problems and didn't have the time to figure things out. Yeah, i had some issues trying to get it working, too. Got the plugins from the boolberry repo working yesterday or the day before and didn't try to get the alias list working. I just looked at what the website was doing and figured out it was just using the output from the rpc call and put curl -X POST http://host:port/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"'get_all_alias_details'"}' -H 'Content-Type: application/json' -o /munin/web/path/aliases.json into cron and adjusted what boolberry.com's javascript was doing a bit to work on my server. I guess I could make it one of the menu options in the pool code with instructions to get munin working there. That might be nice. |
|
|
|
Those stats haven't been working for some time. They were informative but I don't think many people ever looked at them. I used the stats page mainly to see what aliases were available. I'm very busy with my main occupation but I might have time in the next few days to recreate and host them on a crypto related website I'm setting up if you don't get a response from Crypto Zoidberg. He is the person in control of the boolberry.com website. I whipped something up based on what was on boolberry.com. It's at https://cncoin.farm/munin/ if you want to use it. Click on the BoolberryStats link to see graphs. |
|
|
|
Just a warning to miners, you may have to update scratchpad sizes. I have miners connecting and not submitting shares. I noticed my nvidia miner had a scratchpad issue and it's probably happening to everyone using that if they updated the scratchpad size to be We have reached the point past that. You will need to change that, so probably Thank you for telling us this but can you explain in more detail what the meaning of this is and how we change the code exactly? in the source for wolf's miner, edit the file miner.h and find the line #define WILD_KECCAK_SCRATCHPAD_BUFFSIZE (64<<20) It might say <<21 if you have previously edited it last time the scratchpad size got too big. Change it to be 64<<22, save the file and rebuild. Usually that just means typing make. then run your miner as usual. |
|
|
|
Just a warning to miners, you may have to update scratchpad sizes. I have miners connecting and not submitting shares. I noticed my nvidia miner had a scratchpad issue and it's probably happening to everyone using that if they updated the scratchpad size to be We have reached the point past that. You will need to change that, so probably |
|
|
|
Oh, are they giving out to anyone now, or did you sign up for early access or something? |
|
|
|
Maybe you should ask the person who started it. Threads can be locked for many reasons. This thread and the new Boolberry speculation thread should be enough. I don't recall locking it. Hey, how's it been? What you been up to? |
|
|
|
Someone else had this problem the other day. Here's what got them working. Right-click on the shortcut, click properties and add this after the filename --add-priority-node 66.228.33.249:10101 --add-priority-node 59.120.166.36:10101 --add-priority-node 62.201.213.25:10101 --add-priority-node 95.85.21.33:10101 --add-priority-node 107.170.97.197:10101 Not work for me hmm, are you sure you closed it, made the change and started it again? it is here?  No, on my system the tab is called shortcut. Raccourci for you. Just add those after the last quote after qt-boolb.exe", so it looks like qt-boolb.exe" --add-priority-node 66.228.33.249:10101 --add-priority-node 59.120.166.36:10101 --add-priority-node 62.201.213.25:10101 --add-priority-node 95.85.21.33:10101 --add-priority-node 107.170.97.197:10101 at the end |
|
|
|
Someone else had this problem the other day. Here's what got them working. Right-click on the shortcut, click properties and add this after the filename --add-priority-node 66.228.33.249:10101 --add-priority-node 59.120.166.36:10101 --add-priority-node 62.201.213.25:10101 --add-priority-node 95.85.21.33:10101 --add-priority-node 107.170.97.197:10101 Not work for me hmm, are you sure you closed it, made the change and started it again? |
|
|
|
Someone else had this problem the other day. Here's what got them working. Right-click on the shortcut, click properties and add this after the filename --add-priority-node 66.228.33.249:10101 --add-priority-node 59.120.166.36:10101 --add-priority-node 62.201.213.25:10101 --add-priority-node 95.85.21.33:10101 --add-priority-node 107.170.97.197:10101 |
|
|
|
Hello BBR community, I've been dabbling in a bit of coding over the last couple of months and finally can unveil the test version of..... Popboolr. http://popboolr.comPopboolr is a web app game based on real-time Twitter data that allows players to ‘claim’ tweets and earn Boolberry. ...snip... Fun! Thanks for working on this! |
|
|
|
Hello,
i tried downloading the wallet (windows, full installer). The wallet seems not to synchronize with the network. Next i downloaded the blockchain file and placed it in the right folder. After starting the wallet again, a certain amount of blocks have been loaded, anyway there is no progress in synchronization.
Any suggestions?
Thank you.
Right-click on the shortcut and add this after the filename --add-priority-node 66.228.33.249:10101 --add-priority-node 59.120.166.36:10101 --add-priority-node 62.201.213.25:10101 --add-priority-node 95.85.21.33:10101 --add-priority-node 107.170.97.197:10101 I'm not sure how many of those are still around. It's just what I've been using forever on my nodes |
|
|
|
I just ran a Mint 17.2 livecd to test this and I'm seeing the same thing. Looking into it. Nice to see the testing going on. I will run the new db version on Ubuntu later and post if I have any problems My livecd ran out of space when i did an apt-get upgrade and I ran out if time. Now I'm taking care of a sick 1 year old who I think is trying to fall asleep on me. I'll see if I can continue testing in a bit. I clicked on the YouTube link thinking it was a tutorial or something. Hopefully your 1 year old is feeling better now. Thanks. Yep he's feeling better, but the next night my 5 year old was vomiting all night. It's going around here. |
|
|
|
Yeah, I screwed up the build system. You can change the part that says if(CMAKE_CXX_COMPILER_ID STREQUAL "GNU" AND NOT (CMAKE_CXX_COMPILER_VERSION VERSION_LESS 4.9.0))
set(CMAKE_AR "gcc-ar")
set(CMAKE_RANLIB "gcc-ranlib")
else()
set(CMAKE_AR "llvm-ar")
set(CMAKE_RANLIB "llvm-ranlib")
endif()
to if(CMAKE_CXX_COMPILER_ID STREQUAL "GNU" AND NOT (CMAKE_CXX_COMPILER_VERSION VERSION_LESS 4.9.0))
set(CMAKE_AR "gcc-ar")
set(CMAKE_RANLIB "gcc-ranlib")
elseif(CMAKE_CXX_COMPILER_ID STREQUAL "Clang")
set(CMAKE_AR "llvm-ar")
set(CMAKE_RANLIB "llvm-ranlib")
endif()
in CMakeLists.txt. If you were trying to test the db tree, instead of changing the CMakeLists.txt file, just run and redo the cmake line and make again and it should work. My screw ups aren't in that branch. |
|
|
|
I just ran a Mint 17.2 livecd to test this and I'm seeing the same thing. Looking into it. Nice to see the testing going on. I will run the new db version on Ubuntu later and post if I have any problems My livecd ran out of space when i did an apt-get upgrade and I ran out if time. Now I'm taking care of a sick 1 year old who I think is trying to fall asleep on me. I'll see if I can continue testing in a bit. |
|
|
|
I just ran a Mint 17.2 livecd to test this and I'm seeing the same thing. Looking into it. |
|
|
|
getting the following errors when compiling from git: Linking CXX static library libcommon.a
Error running link command: No such file or directory
make[3]: *** [src/libcommon.a] Error 2
make[3]: Leaving directory `/home/nanashi/.boolb/boolberry/build/release'
make[2]: *** [src/CMakeFiles/common.dir/all] Error 2
Linking CXX static library libcrypto.a
Error running link command: No such file or directory
make[3]: *** [src/libcrypto.a] Error 2
make[3]: Leaving directory `/home/nanashi/.boolb/boolberry/build/release'
make[2]: *** [src/CMakeFiles/crypto.dir/all] Error 2
make[2]: Leaving directory `/home/nanashi/.boolb/boolberry/build/release'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/nanashi/.boolb/boolberry/build/release'
make: *** [build-release] Error 2  mint 17.2 Did you install build-essential first? |
|
|
|
what makes the leveldb integration at boolberry different than what monero is doing? Or it is somewhat similar?
The leveldb here is only being used to store list of blocks, not all the other in-memory stuff that makes up a node (transactions, block index, output indexes, etc.). Monero moves all that stuff to the DB. Advantages of BBR approach: 1. Simpler to implement and get right 2. Some operations still using the in-memory data may be more efficient Disadvantages of BBR approach: 3. Higher remaining memory usage (but with BBR's pruning and lower volume of usage, probably not too bad) 4. Some possibility of inconsistencies between the two data stores in-mem and database (clintar's fix addresses one instance of this) 5. Still requires the periodic "save blockchain" timer, which pauses many daemon functions during the saving process (though the process should be faster without needing to save the block list) #1 is pretty significant IMO. Given that these projects are all works in progress, building the ultimate solution on the first go is not aways the best approach. EDIT: added #5 Yeah, #5 is probably the main reason I'd like to see everything changed to db. I might try to tackle that based on cz's main blocks changes. |
|
|
|
Is the other instance you refer to if the saved blockchain is more recent that the lmdb database (which I'm not sure how that would happen in practice unless you copied a newer blockchain.bin where there's an older db), or are you talking about something else?
Just in general that the process isn't transnational the way an ACID database commit normally would be so things can go wrong in various ways. Without carefully auditing the ordering of events and the behavior of various operating systems it is hard to be 100% sure what failure modes are possible. For example, another failure that occasionally happens on Windows (for all cryptonotes) is the blockchain.bin file gets corrupted during save since there isn't a really good way to replace a file atomically (on Linux you can rename-replace, which mostly works). This would leave you with a valid database but an invalid blockchain.bin. Of course this would probably be no worse than the previous (no db) case, but would be worse than the full db case. This is fixable, but somewhat annoying to fix, especially if all the data is going to end up in a database eventually anyway (I have no idea as to your plans). BTW, in case my comments were not clear I do think this is nice work by crypto_zoidberg and clintar. Ok, thanks for the input. Just wondered if there was something I should be looking into I hadn't thought of. I don't really know the plans, either. Just was contributing what I came up with as a work-around. I agree having everything in the database does take care if these issues, too. Pretty slick how cz implemented the db, though, huh? At least I thought so. Anyone have any suggestions for things they want to see in the codebase? |
|
|
|
|
Show Posts
