Topic: ANN - [BEE] - 2014 -2018 - BEE COIN - the original BEE === - page 5. (Read 27499 times)

what makes you think that?

So it is unsuccessful takeover

Yes I did, sorry for the lack of response. In order to construct a coherent and accessible non-technical description of the problem, one first has to understand the nature and detail of the problem.  Usually, laying bare the nature and detail of the problem is a direct precursor for a solution, as it proved to be in this instance so I chose to implement the solution first and write about it later.

I've got this far;

I'll restrict my comments to addresses, preferring to leave the emissions control system until I've constructed a more detailed mental model of its structure and functioning. I'm not completely out of the woods yet ...
The UTXO set/public ledger transfer is eye-wateringly detailed here: https://github.com/gjhiggins/been/blob/bee/src/chainparams.cpp#L46 and initial results are very promising.

Previously, I just used an arbitrary address and a 1234567890 balance conjured out of thin air, worked okay a coupla months ago:



This time out, I created three additional pub/prv address pairs, funded from the community chest and I parked them at the front of the queue so I could check whether the advertised “do it in the genesis block” solution actually worked:



This is all from the current code as committed to the repos. If you can compile up a Linux binary of Bee Core (I haven't got round to working out how to adjust the gitian build system to generate Windows/OSX binaries) then you can import your privkey(s) into it and check whether your UTXO balance i) shows up at all and ii) is accurate. I hope this works as described, it is the most transparent solution. But if not, there are other ways of skinning this particular cat such as a hacking the reward calculation to yield a humungous premine (the unspent total UTXO set) in block 1, credited to a distro address and use the rest of the blocks mined during  the stabilisation period to turn the premine back into the UTXO set simply by sending the corresponding calculated balance to each address until the premine's all spent.

For those who like to work things through for themselves ...

It's the PoS thing, see. AFAIK there are only two PoS alts cloned from Bitcoin Core > 0.10, PIVX and Navcoin.

The technical cost of ownership of PIVX’ complex architecture and functioning puts it currently out of reach of the Bee community (that's my informed assessment). And anyway, PIVX is a clone of Dash and is basically Core 0.11 with Dash additions - I'm unsure whether it includes CLTV (enables decentralised exchange ops).

OTOH, NavCoin is a clone of Bitcoin Core 0.13 (mostly 0.13.1, with a few elements from 0.13.2) adapted for PoS and augmented with some centralised anon servers. CLTV is a feature of 0.13 so decentralised exchange ops are available from the get-go.

Bitcoin Core 0.10 changed the protocol, optimising and reducing the amount of data being sent over the wire, effectively throwing a terminally large spanner into the stake calculator engine (Bitcoin devs couldn't care less). And this is why the vast majority of PoS alts are still running on clones of 0.8.X (attested to by the presence of a qmake .pro file) - a few may have have upgraded to Bitcoin Core. ... okay, I had to check my model against reality and it holds true for all the Bitcoin clone PoS alts in the top 86 alts on coinmarketcap ... Bitcoin Mechanic claimed to have a solution, albeit not quite complete but it didn't get far. I think the 0.10 optimisations stopped carrying the date of each of the txs, deemed necessary to calculate coin age. At least that what I'm inferring from Hans Robeer's solution for PeerCoin - AIUI, his insight is: for the limited purposes of coin age calculation, using the block time as a proxy will suffice. I suspect this is how Navcoin also solves the problem, given that they're adding nTime back into the CTransaction class definition:
Bitcoin Core 0.13.1: https://github.com/bitcoin/bitcoin/blob/03422e564b552c1d3c16ae854f8471f7cb39e25d/src/primitives/transaction.h#L371
Navcoin: https://github.com/NAVCoin/navcoin-core/blob/master/src/primitives/transaction.h#L408

Aaanyway, the overall plan was/is to do some basic re-branding, strip out the anon stuff to leave a vanilla Core 0.13 PoS coin, switch in the key Bee parameters and insert the Bee UTXO/public ledger.

What I'm stuck on atm is the PoW instamine that kick-starts the blockchain. Because Bee is basically just Navcoin-rebranded code and Navcoin kicked off with a PoW period before changing over to 100% PoS (as hashrate from staking took over from hashrate from mining), Bee needs to follow the same pattern (except that as we don't need incentivising to mine a few BEE blocks, any generated during the PoW will accrue 0 BEE reward). The coins in the transferred ledger should be ready for staking as soon as the importprivkey returns, so it seems reasonable to expect stakehash will pick up reasonably promptly.

Part of the problem is that Navcoin's own PoW and emissions control code has been untouched since they switched to 100% PoS aaaages ago and the rest of the codebase has since moved on and there may yet be unresolved issues in that department but on the face of it, those tests that are expected to pass (i.e. they do with Navcoin) do pass, looks like the engine is assembled okay, it turns over, starts and even runs, briefly and now it becomes a matter of adjusting the carburettor/timing settings, so to speak. I just have to study the code a bit more and make intelligent use of the QtCreator debugger (a very acceptable IDE, IMO).

The trouble is, I don't often get blocks of uninterrupted time so progress tends to be in fits and starts.

Cheers

Graham

Thanks for this update graham that is great news that you are still working away on it.

Many do not realise including myself really how much work it is to revamp a coin especially to an up2date codebase.

I think discussion on thread is the best way forward because sending me Pm;s about technical aspects is fruitless since I am not a coder at any level.

I will 100% help beecoin with what i can do which is get people interested in good projects and also try to ensure things are done as fairly as possible along the way.

But technical matters are not something I can make answers on at all.

BTW Graham did you get my PM regarding setting up a foundation BTC address to accumulate BTC for exchange listings and other things where they only accept BTC or fiat like a server and such?

I am quite happy for you to hold the btc community chest. We could start auctioning off bees now to raise some funds for these things. Then the raised BTC you can allocate to what things you think are best after the code base is released.

During this downturn may be the best time to secure some exchange listings even if we dont list it up until the new codebase is ready and tested.

I want to assure everyone I certainly have not abandoned beecoin and i am not ignoring anyone. I am ready to start pitching in as soon as there is something I can actually do. I would like to see many tasks for everyone that they can complete to enhance bee and also get rewarded for their time and effort. That would be the best way forward as far as I am concerned.

What is the algo on this and do you need a pool for it ? if so let me know Ill put it up on Dpool.io

Your guess is as good as mine, what do you think of it so far? https://github.com/gjhiggins/been/commits/bee

Bee's been getting around 50% of my available effort overall, 80% recently. Available effort is frequently compromised by local constraints.

I will urge people not to underestimate the effort demanded by this kind of activity:

https://bitcointalksearch.org/topic/m.27568755

I can now generate blocks, so am setting up a small network to check whether staking works.

Cheers

Graham

Guys any eta on the new code base? It has been quite some time since we had an eta? I am afraid BEE will get left behind.

just to say... i;m not ignoring any PM's at all its just best and easier to discuss everything on thread.

So yeah thanks for those of you who have offered to build the website or do other work in design or seo.

This is all great and we will certainly do that in the near future.

We just need to finalise some details and the next step is websites and exchanges etc.

I have been looking at a few exchanges and some of those are quite expensive however there are a few more reasonable ones.

It is not a good idea to list beecoin just yet because when we redesign beecoin it may need to be relisted and we will have to pay 2x.

Sometimes it takes quite a while to upgrade a crypto so just a bit more patience and we will hopefully see beecoin rebooted

As i have said i am not a coin developer myself so any technical questions of a deep level are not best sent to me, post them on the thread.

Don't worry beecoin will have other ways to find itself inside yours and others portfolios. Micro task and a beelievers wage packet each week would be the way I would like to see beecoin go in future.

This is a wonderful project with a strong team of managers! I want to have in your portfolio a few coins BEE, but I'm a crypto-newbie, and I have no bitcoin or more etherium to buy Beecoin

Thanks for the progress - I am too busy

Thanks for your kind offer to help bee design a new website. This is exactly the type of community involvement that is great to see.

As soon as a few more details are ironed out by graham regarding the codebase final name ...and we get certain logo developed then this will be the time to start a website development plan.

thanks for your offer

Not so long ago learned about Your project - Beecoin. This is a wonderful project with a strong team of managers! I want to have in your portfolio a few coins BEE, but I'm a crypto-newbie, and I have no bitcoin or more etherium to buy Beecoin   My question is this: will you have another bounty of the company, I will join with great desire!

Quote from: qubii on January 05, 2018, 11:42:04 PM
It shows a bunch of incoming transactions - but the total is not reflected in this.

You mean actual Alice-to-Bob txs or stake rewards - if the latter are these not merely orphans?

Cheers

Graham

(Pls forgive the brevity, busy atm)


I mean Alice-Bob.

No worries on replies - you must be a 'reet busy chap

If blockexplorer I cant hunt myself and get back to you.
Or can send on info in PM - no rushes.

Regards

Greetings.  I do not own any Beecoin, but recently discovered its existence by doing an Internet search for "beecoin" on a whim due to my love of bees.  I read through the last year or so of posts over the last few days.  It seems I had fortuitous timing as things appear to be moving forward toward a relaunch.

If I am reading correctly, you are still in search of a website developer.  If that is the case, I'd be interested.  I am happy to front my own money to register a domain and pay for hosting and then handle the design.  I did a preliminary search and there are a few good options available.  Perhaps it would be best to discuss via PM to prevent some jerk from quickly registering the desired name once one is agreed to?

Also, does anyone know the old Twitter user's login info?  It would be good to revive that.

Finally, I will give my thoughts on the rebranding: I would go with just "BEE" for the official name ("bee coin" informally to note the crypto currency.)  There seems to be some unspoken consensus on that as the way to move forward and offers the most marketing opportunities, IMO.



(FYI, I've been a user of crypto since 2012 or 2013.  I had a Bitcointalk account year ago, but it seems it was disabled due to a 2015 hack, so I'm starting a new one.)

wow.. i will waiting the new codebase of BEE, this will be interesting to join BEE Coin project, hope progresing in the redevelopment will be done.

Thanks for the support guys we hope to bring good opportunities here to earn a nice bee wages in the near future so check back from time to time.

Good luck, nice to c u.

I understand and support you, good luck again