Topic: [ANN] [BEE2] [BEECOIN V2] POW X11/POS Hybrid - Now With CLIENT CHAT Feature! - page 5. (Read 133406 times)

Just curious but do we still plan to stick BEE coin name? Maybe a re branding might be in order. Just my 2 cents. Let me know your thoughts. Perhaps make a poll?

Patiently waiting for this coin to get refreshed and rebranded. This coin still has a lot of potential and was fairly distributed.

So this coin turned into B3?

hi, any beecoin founder here?
I have a serious proposal to make.

Sorry so what is happening with this coin? Are we re-branding or swapping coins? Interested to see this coin get back on its feet.

Cheers for the update graham. Thanks for everything you have done.

It is great to see things moving along for beecoin.

Whilst the code based development is ongoing I wonder if the community can help think up useful tasks we can offer to people to earn the new upcoming bees?

Also what does everyone think about start a new fresh thread once we are running with the new code base?

First thing we could really do with is a nice website for beecoin anyone have or know any great web designers?

What other tasks or micro jobs could be given out to people to do for payment in bees that would help in building the community and also give incentive to accumulate and hold beecoin?

I sent this explanation to cryptohunter ...


The other comment I made ...

Cheers

Graham

i mean just updating beecoin to a more modern functional coin with anon and masternodes would be great. This takes time too though.

smart contracts, atomic swaps etc all would be great of course but then you would probably need a gigantic dev team on board.

Your analysis is spot on. I did a re-branding of PIVX but didn't change the coin's parameters, so it promptly synced with the PIVX blockchain. A short time afterwards I came across Max Guevara's dismissal of the PIVX code as “buggy” ¹ and - well, whatever they say about him, he does have the technical chops and I must admit, I did get a sense of something vaguely similar in the early days (prior to it rebranding as PIVX).

So I took a long look at an alternative, a Core 0.13 PoS coin - no masternodes but otherwise okay, to wit Navcoin. It too is a quite a challenge - it's got an idiosyncratic anonymising solution that needs stripping out. I got some way into it before realising that it was going to take quite a bit of time to work through and maybe I'd better return to my adaptation of PIVX to have something to deliver to the community.

However, when I returned to PIVX and changed the coin params to match Bee's, I hit a bug. There's an issue somewhere in InitBlock but the error object that is supposed to be instantiated by the surrounding try/catch structure (https://github.com/PIVX-Project/PIVX/blob/master/src/main.cpp#L4787) is uninstantiated for some inexplicable reason. So debugging just fails because the error message is buggy in that the error is that the error object hasn't got an error message string to print.

All I can do is undo the changes, check that it still runs then carefully re-make each change in an attempt to work past the problem. There are some serious mismatches in, e.g. number of coins, which may impact how the chain functions.

I don't know of any other than the two decentralised exchanges (I forget the names) which basically just require that CHECKLOCKTIMEVERIFY is available. Navcoin has the CHECKLOCKTIMEVERIFY op-code, PIVX doesn't (to my slight surprise, until I recall that it is in essence a Dash clone and a fork of Bitcoin Core 0.10). And that complicates the situation quite comprehensively - exchanges being quite so crucial to PoS coins in terms of enabling people to join the community.

In the interim, I shall push the PIVX work up to Github in case anyone can throw some light on the issue. I'm also re-visiting Navcoin to see if I can get a better handle on how much hacking around will be necessary to strip out/disable the anon code.