Bitcoin Forum
May 28, 2024, 02:51:38 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [BBR] Boolberry: Privacy and Security - Guaranteed[Bittrex/Poloniex]GPU Released on: October 21, 2017, 08:23:40 PM

There's no 'outsiders' here, if you're a BBR holder then you're part of the community Smiley Our development plans will be made public soon.

You're more than welcome to join the team meeting on Monday, just shoot me a PM. That invitation is also open for anyone else that wants to join our development efforts and provide technical value to the planning session. I want to include as many potential contributors from the community in this process and also after the project reveal. After all, this is a community project.

Thanks for the openness ... sounds interesting ... if only time would not be in such short supply ...

But for what it's worth, I write down a sketch of the result of my brainstorming. (Don't trust a random poster with less than a dozen posts too much, however.)

As I wrote already, it is based on my assumption (which may be false, who knows) that the technological differences between current and future Boolberry are simply too great to introduce it in the form of a single program that is able to "smoothly sail over a hard fork block height", so to say.

For the following let's call current Boolberry Boolberry Classic. A first hard fork brings to life its successor, Boolberry Intermediate, and the second hard fork introduces the real destination, Boolberry NT (for "new technology", of course).

Boolberry Intermediate is a true hard fork: A new version for transactions forces people to decide whether they follow and install it, which is a "Yes" vote for the whole endeavor, or whether they reject it and want to stay Boolberry as it is - a "No" vote.

Boolberry Intermediate is basically the current codebase, fully compatible, but with some crucial code added to manage the switchover to the new, incompatible blockchain: It is programmed to flat-out refuse adding any more transactions at and above the height for the second hard fork, so that basically the old chain can be "stopped" in an orderly way.

Furthermore, some yet-to-design mechanism would make it highly improbable that there will any competing chains in the last few blocks before the second hard fork height, of all things. Maybe be a single, temporary and single-purpose Boolberry masternode that is the only one with the power to mine the last few blocks, to really minimize the danger that the old chain ends in disagreement?

With the old chain "stopped", Boolberry NT can pick everything up and continue.

So that's my two-hardfork idea. If the introduction of Boolberry Intermediate fails, it's clear already rather early on that the project in the planned form does not fly, which I see as positive because it allows adjustments. If it succeeds, you have installed the necessary mechanisms for the switchover.
2  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [BBR] Boolberry: Privacy and Security - Guaranteed[Bittrex/Poloniex]GPU Released on: October 21, 2017, 04:31:04 PM
The new direction is to do a snapshot of BBR blockchain and import that into the new codebase.

Isn't this simply known as a hard fork in crypto currency space? Where you always have the potential problem that the old chain lives on?
Yes, but if you look at the history of other cryptocoins, the likelihood of such forks living on is quite low.

A centralized coinswap is much worse in this respect, IMHO. I'd certainly be wary of sending all my coins to a "trusted" party, and I'd seriously look into maintaining a "classic" version. In contrast, it is much easier to simply update your software and accept the fact that old clients are no longer compatible.

I am an outsider, and I don't know what is planned the "new" Boolberry of course, but I would also say to hard fork the blockchain as seamlessly as possible is "the way to go", and "they way it's done", and if it's done properly, people will keep faith and mostly migrate to the new chain.

I have a hunch that part of the problem might be a difficulty for the new daemon to read the serialized blockchain of the old daemon, so that you can't just switch at a given block height within a single program, but must orchestrate a "daemon switch" of sort as well. A fascinating problem, if true, that got me thinking and has my head spinning. I currently brainstorm that I would probably try to do this with two hard forks...
3  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [BBR] Boolberry: Privacy and Security - Guaranteed[Bittrex/Poloniex]GPU Released on: October 21, 2017, 03:35:38 PM
The new direction is to do a snapshot of BBR blockchain and import that into the new codebase.

Isn't this simply known as a hard fork in crypto currency space? Where you always have the potential problem that the old chain lives on?
4  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [BBR] Boolberry: Privacy and Security - Guaranteed[Bittrex/Poloniex]GPU Released on: August 24, 2017, 07:36:49 PM

Ok, put up my latest code.
https://github.com/clintar/boolberry/tree/lmdb_scratch

i'm to the point where the blockchain syncs (pretty quickly) but if there are alternative blocks, it falls down, which makes some coretests fail. and i can't get a testnet set up to start mining from zero, or maybe even mine a block against this code. Haven't had time since I got the latest committed. should be able to just do
Code:
make -j4 build-release 
or
Code:
make -j4 build-debug
or
Code:
make -j4 build-debug-testnet
to get the thing to compile now (assuming required dev packages are installed). Please if anyone can help look at it, it would help a ton!

passing
Code:
--seed-node 88.197.53.159:10101
should get it syncing

I tried it. Worked like a charm for me, it downloaded the whole blockchain in around 90 minutes.

I did not let it run long enough to encounter a chain reorg, however.

Any tests that would be particularly valuable, beyond just running it and letting it download the blockchain?
5  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [BBR] Boolberry: Privacy and Security - Guaranteed[Bittrex/Poloniex]GPU Released on: August 06, 2017, 03:13:51 PM
If anyone wants to test out my latest db code, I have it at https://github.com/clintar/boolberry/tree/lmdb_scratch

you can get the branch with
Code:
git clone -b lmdb_scratch https://github.com/clintar/boolberry.git
then
Code:
mkdir -p build/release; cd build/release
cmake -DDATABASE=lmdb ../..
make -j4 daemon
should compile it, at least in linux. Let me know if it compiles or not at least! Smiley

I tried this branch. It compiled without problems. The produced binary started and created an initial db file of about 1 GB.

There is no file conversion yet from the "old" .bin format to lmdb format, so it wants to sync the blockchain from start, even with a blockchain file within reach, right? At least that was what it did on my system.

Sync immediately ran into problems however. I had repeated messages as follows:

Code:
2017-Aug-06 13:37:10.273809 [P2P3][193.70.85.9:10101 OUT]Block verification failed, dropping connection

These messages come from currency_protocol_handler.inl, line #377 (as checked out from GitHub today):

Code:
        if(bvc.m_verifivation_failed)
        {
          LOG_PRINT_CCONTEXT_L0("Block verification failed, dropping connection");
          m_p2p->drop_connection(context);
          m_p2p->add_ip_fail(context.m_remote_ip);
          return 1;
        }

Sync stuck forever at block 3 with repeated messages like this one:

Code:
2017-Aug-06 13:37:09.362602 [P2P7][193.70.85.9:10101 OUT]Sync data returned unknown top block: 3 -> 840955 [840952 blocks (1167 days) behind]

Is it supposed to be able to sync with "conventional" Boolberry nodes?
6  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [BBR] Boolberry: Privacy and Security - Guaranteed[Bittrex/Poloniex]GPU Released on: August 02, 2017, 08:19:11 PM
I am new to Boolberry and in the process of setting up a full node. I am currently using a debug build of Clintar's db_changes branch on a recent Debian Linux. (I save testing the lmdb_scratch branch for later.)

...

But one thing worries me: I get a lot of WRONG NETWORK AGENT CONNECTED! messages from the daemon, and after a while it even starts to ban ip's.

...

Or still something not quite right with my new node?

Strange, I ran a release version of that all day and never got anything like that. I was going to edit this saying I updated the repo with some fixes. I thought I did before, but I guess not. Try it now.

Well, thanks for the fast repo update! I will have time to compile a new version from it and test probably this coming weekend.

But anyway: Yesterday I was running the daemon in a quick-and-dirty way on the non-standard port 50001, because of problems with port forwarding / NAT; today I switched to the standard 10101 port, and presto, no more "wrong network agent connected" messages. Maybe there is still a small bug somewhere that triggers when using --p2p-bind-port ...

By the way, is this forum here the right place to discuss such rather technical matters and problems? Maybe better to open issues on your GitHub repo for such things? Would be no problem for me.
7  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [BBR] Boolberry: Privacy and Security - Guaranteed[Bittrex/Poloniex]GPU Released on: August 01, 2017, 07:55:12 AM
I am new to Boolberry and in the process of setting up a full node. I am currently using a debug build of Clintar's db_changes branch on a recent Debian Linux. (I save testing the lmdb_scratch branch for later.)

It seems to run alright. I could sync the blockchain in less than a day, using the 5.9.44.154:10101 seed node that I found on the boolberry subreddit. I get new blocks and new transactions, and everything like current height is in agreement with the new blockchain explorer that went up yesterday (great work, by the way, congrats). Finally, other nodes can connect to my daemon; currently I have 4 incoming connections.

But one thing worries me: I get a lot of WRONG NETWORK AGENT CONNECTED! messages from the daemon, and after a while it even starts to ban ip's.

What is happening here? Boolberry nodes running outdated software versions getting rejected from my (hopefully) up-to-date daemon? Daemons of another Cryptonote currency trying to connect to my Boolberry node? Or other programs altogether that just happen to use the same ports as Boolberry?

Or still something not quite right with my new node?
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!