ANN - [BEE] - 2014 -2018 - BEE COIN - the original BEE ===

[cryptohunter]

This will be the continuation of beecoins up to date thread.

Old threads

https://bitcointalk.org/index.php?topic=461550.0 ---------- original BEE coin thread from 2014

https://bitcointalk.org/index.php?topic=559876.0

https://bitcointalk.org/index.php?topic=601247.0


I noticed some new projects trying to take the BEE ticker. We should post here to make our intentions known to retain this ticker for BEECOIN the original BEE.

This OP will be updated in due course as the project is progressing and still in the redevelopment stage.

We are expecting the new codebase of BEE to be released shortly so check back for chances to earn BEE coins and join this project.

[1715130770]

1715130770

[1715130770]

1715130770

[1715130770]

1715130770

[1715130770]

1715130770

[htao]

Yap, this is the original BEE.

It had it's problems, but it's still around and it may do a strong comeback this year 

[mayla alma]

I understand and support you, good luck again

[michailr]

Good luck, nice to c u.

[cryptohunter]

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.

[herfianto]

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.

[BEEcoiner]

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.)

[qubii]

<quote>
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)
</quote>

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

[icodetected]

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!

[cryptohunter]

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.)

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

[GREEDYJOHN]

Thanks for the progress - I am too busy

[moirahpascual11]

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

[cryptohunter]

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

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.

[cryptohunter]

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.

[Real_Unhooked]

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.

[gjhiggins]

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.

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://bitcointalk.org/index.php?topic=721936.msg27568755#msg27568755

Start-of-year forward: I am looking at forking PIVX and studying other projects that have successfully and unsuccessfully done so. Of course, a gigantic effort will be needed. The PIVX codebase is very mature and will offer Sterlingcoin users all the features of a state-of-the-art cryptocurrency they may expect in 2018. PoS reward and supply will not change, so long as the community agrees. No ETA or more specifuc details can be given at this time. Many details have to be sorted and much work before more than that can even be said. Of course, this will make for a very exciting 2018 for Sterlingcoin holders. Some work and experimenting has started, but only at a research level. Familiarizing with the code and even some of the functions. I hope to be devoting full-time hours on the task in the very near future. I will report on that.

https://bitcointalk.org/index.php?topic=721936.msg28795933#msg28795933

To be clear, it is not a PIVX "partnership" per se. The PIVX code is open sourced. We are aiming to fork it, modify it to our needs, and then release it under the Sterlingcoin name. It is normal in open sourced software and very normal in cryptocurrency. Of course credit will remain to the many PIVX developers and done with respect to them all. We have been having some of those discussions in our Discord and all are welcome. It is a very pain-staking process. It will require much time and an ETA cannot be given at this time. I apologize, but there are still too many unknowns to do so with any certainty.

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

Cheers

Graham

[Coryvmcs1]

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

[cryptohunter]

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.

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://bitcointalk.org/index.php?topic=721936.msg27568755#msg27568755

Start-of-year forward: I am looking at forking PIVX and studying other projects that have successfully and unsuccessfully done so. Of course, a gigantic effort will be needed. The PIVX codebase is very mature and will offer Sterlingcoin users all the features of a state-of-the-art cryptocurrency they may expect in 2018. PoS reward and supply will not change, so long as the community agrees. No ETA or more specifuc details can be given at this time. Many details have to be sorted and much work before more than that can even be said. Of course, this will make for a very exciting 2018 for Sterlingcoin holders. Some work and experimenting has started, but only at a research level. Familiarizing with the code and even some of the functions. I hope to be devoting full-time hours on the task in the very near future. I will report on that.

https://bitcointalk.org/index.php?topic=721936.msg28795933#msg28795933

To be clear, it is not a PIVX "partnership" per se. The PIVX code is open sourced. We are aiming to fork it, modify it to our needs, and then release it under the Sterlingcoin name. It is normal in open sourced software and very normal in cryptocurrency. Of course credit will remain to the many PIVX developers and done with respect to them all. We have been having some of those discussions in our Discord and all are welcome. It is a very pain-staking process. It will require much time and an ETA cannot be given at this time. I apologize, but there are still too many unknowns to do so with any certainty.

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

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.

[gjhiggins]

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?

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;

Code:

getinfo
{
  "version": 13000000,
  "protocolversion": 70016,
  "walletversion": 130000,
  "balance": 0.00000000,
  "newmint": 0.00000000,
  "stake": 0.00000000,
  "blocks": 5,
  "timeoffset": 0,
  "connections": 2,
  "proxy": "",
  "testnet": false,
  "keypoololdest": 1513046497,
  "keypoolsize": 100,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

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 ...

Code:

2018-01-25 01:40:28 ERROR: ContextualCheckBlock() : incorrect proof-of-work at height 5, 1e0fffff / 1e0f095b
2018-01-25 01:40:28 InvalidChainFound: invalid block=000008324[...]6906668  height=6  log2_work=22.807356  date=2018-01-25 01:40:28
2018-01-25 01:40:28 InvalidChainFound:  current best=00000c054[...]4ce9a80 height=5  log2_work=22.584964  date=2018-01-24 23:16:40

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

[cryptohunter]

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?

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;

Code:

getinfo
{
  "version": 13000000,
  "protocolversion": 70016,
  "walletversion": 130000,
  "balance": 0.00000000,
  "newmint": 0.00000000,
  "stake": 0.00000000,
  "blocks": 5,
  "timeoffset": 0,
  "connections": 2,
  "proxy": "",
  "testnet": false,
  "keypoololdest": 1513046497,
  "keypoolsize": 100,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

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 ...

Code:

2018-01-25 01:40:28 ERROR: ContextualCheckBlock() : incorrect proof-of-work at height 5, 1e0fffff / 1e0f095b
2018-01-25 01:40:28 InvalidChainFound: invalid block=000008324db632305e37e87b75b09383c9888b34b7d8137ab10b8ab1c6906668  height=6  log2_work=22.807356  date=2018-01-25 01:40:28
2018-01-25 01:40:28 InvalidChainFound:  current best=00000c054ed5d6d24d6bc68fcae092cedd6aa02e522fd4d915d1499c04ce9a80  height=5  log2_work=22.584964  date=2018-01-24 23:16:40

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 very informative response.

I think most people including myself can not even start to imagine how complex and vast this kind of project is at a deep level.

The great thing is that (i hope i am correct here ) that when you have finally worked out all of this in depth technical stuff and even solved all of these bugs and hurdles from start to finish you yourself will have now a complete understanding of a lot of the mechanisms these coins work upon. So really you are turning yourself into a fully skilled crypto developer. I know already you are a computer scientist but I guess there are different areas and not many study specifically crypto develeopment.

Now the thing is i know you are busy and that in real life so you can;t like go full time crypto dev (not that any sane person would want to) but to maybe speed things up. Are there any specific questions that right now are holding you up that i could post to a few devs I sometimes speak with and ask them if they could give you a specific response (because maybe they have done or gone through the exact thing you are going through right now before) and their answer may save you a bit of time?

If so then if you PM me any direct specific question( i wont understand it) but then I can maybe post it to them and see if they can give us any tips.

Also do you mean because we are trying to conduct this upgrade in the fairest way with this kind of auto balance shift to the new chain that it is proving to be much more complex than if we just forked nav coin and did a coin swap over to the new code base like that?

[lipton]

So it is unsuccessful takeover

[cryptohunter]

So it is unsuccessful takeover

what makes you think that?

[wsmolive]

I am have some BEEv2 coins ,it is the same the beecoin??  I remember the coin had swapped in 2014 once.

and now the second swap??  or just change the name?

[cryptohunter]

I am have some BEEv2 coins ,it is the same the beecoin??  I remember the coin had swapped in 2014 once.

and now the second swap??  or just change the name?

those coins are still beecoins

soopy changed to bee version 2 but we never agreed to change the project name frome beecoin that was just so the thread was not confusing.

beecoinv2 is beecoin still.

so yes your coins are still valid now.

the way graham is planning to switch will not leave people behind (i think that is true)

If maybe we cant get the swap to work that way then we will just do a usual swap and hopefully people will switch over in good time.

[nlrobbie]

Is this the old beecoin from 2014? So yes, i got a good stack of this coin on a broken hdd. I mined a lot of beecoin that time. If i let the hdd repaired will i be able to synch my old wallet.dat with the blockchain?

[cryptohunter]

Is this the old beecoin from 2014? So yes, i got a good stack of this coin on a broken hdd. I mined a lot of beecoin that time. If i let the hdd repaired will i be able to synch my old wallet.dat with the blockchain?

I am not sure, did you swap those for beev2 in believe that swap was 2015-2016?

[pass75]

[...]
Is maybe there a problem in the wallet that cannot transfer all the coins to a new wallet? no, it just takes time
[...]
Trying to move them little by little it seems it allows me to transfer (per time) approx half of the coins I have in my wallet. this is the way to do it
[...]
I think it would be the best solution to have a slim wallet file with not so many transactions inside. aka “housekeeping”

You'll lose some stake weight in the initial rounding up of the “micro-stake rewards” but that's to be expected. Doing this housekeeping on a regular basis in the future will better preserve stake weights.

Cheers

Graham

Hi Graham, thank you very much... At the end I could move all my coins to a new wallet even if it was a bit hard.
First of all I had to start my old wallet with the -staking=0 option and wait some days all my coins could go out from the staking process and be available for spending.
Then I started to move my coins to a new, fresh and empty wallet: in the beginning with big transactions and then, time by time smaller and smaller. Anyway no more than 30-40% of the available balance. I could understand it was a problem of fees or block dimensions. Infact the last coins I moved were the consolidation of thousands of micro input transactions (due to long staking) that could saturate the fees or more probably the block dimensions.
All was done in about 20 transactions.
IN ALL THIS STORY I WAS REALLY IMPRESSED HOW FAST THE TRANSACTIONS WERE PROCESSED AND CONFIRMED ON THE BEECOIN NETWORK. REALLY REALLY AMAZING COMPARED TO MANY MANY OTHER CRYPTOS!!!
It's the prove this coin was really well done.
I'm sure you could notice this on your own and I'm sure, with your efforts, you are doing it even better ;-)
I'm sorry I cannot help you with the code (I'm not a programmer) but if there is something I can do do not hesitate to contact me.
At the moment I confirm my beecoin node is online 24/7 and I also set up a backup node also online 24/7 to keep the BeeCoin network alive and strong.
Thank you very much for giving your precious time and work to this old, forgotten but also good coin.
Ottavio

[gjhiggins]

So really you are turning yourself into a fully skilled crypto developer.

It's not my intention. I'm a cognitive psychologist by discipline and a cognitive scientist by profession, the latter mainly defined by its use of computational models as investigative tools (hence my broad but patchy knowledge of programming / software engineering --- it was acquired pragmatically and in a piecemeal fashion). Although local constraints circumscribe my involvement to that of a hobbyist, if I had a professional interest as such, it would be in what you might be forgiven for thinking is a bit far-fetched but is very real and also very pertinent to altcoin communities: aspects of Theory of Mind as they pertain to collective intelligence.
https://phys.org/news/2015-06-intelligence-online.html
https://gfbertini.wordpress.com/2016/04/25/theory-of-mind-predicts-collective-intelligence-equally-well-online-and-face-to-face/

For convenience:

Have you ever wondered what factors may shape the interactions we have in online chatrooms? With the advent of the Internet 20+ years ago, the ways in which we communicate have drastically changed, allowing us to easily interact nonverbally or anonymously. Whether it's in a chatroom, email thread, or an online forum, most of us have taken part in some form of group communication on the Internet. Maybe, unbeknownst to us, we became a part of the group's collective intelligence, a form of group intelligence that can surface after collaboration and competition among individuals in the group. But some scientists are wondering, how can we measure the ability of others to communicate in a group, and how can we quantify the effectiveness of a group?

Two traits that make us "distinctly human" are our abilities to empathize and to interact well in social settings with others. These traits are usually measured in face-to-face situations, and may be more difficult to measure online, away from in-person social cues.

One factor that correlates to overall collective intelligence is "Theory of Mind" (ToM), or the ability of one individual to understand the mental state of another and recognize it as distinct from their own; what some may consider "mind reading." In a recent PLOS ONE study, MIT researchers tested the hypothesis that ToM, which can be used to predict collective intelligence in collaborative face-to-face tasks, can almost equally predict collective intelligence in online collaboration. One individual's ability to "read" the behavior of another individual can help contribute to successful communication and overall group intelligence. More than that, this ToM ability may exist even where verbal communication is prohibited, and may contribute to successful communication within an online group.

I'm applying an altcoin context to the questions: “how can we measure the ability of others to communicate in a group, and how can we quantify the effectiveness of a group”.

Except that I'm changing the question away from measurement and quantification to: “how can we best support ...”

Basically, my interest is in understanding the user task information requirements - what information is required to perform a specific task and how it should be presented to best support the process (of creating and maintaining accurate mental models of others).

Are there any specific questions ...

Unfortunately not. The Navcoin clone of Bitcoin Core 0.13 was an exercise in expediency, with parts of the code short-circuited in order to simplify the initial PoW phase - which I hadn't expected, so wasn't looking for.

It's because by the time Bitcoin Core 0.13 was released, the block generation part of the in-wallet miner had been completely obsoleted on mainnet by the shift to ASIC mining and the functionality/API had been adjusted to assume a testnet context with setgenerate (create blocks via continuous hashing) giving way to generate/generatetoaddress (create blocks on demand).

I tried the x11 miner without success and stopped at that point. So I'd had to use generatetoaddress to hand-crank the blockchain. What I hadn't spotted was that the API block generation code generated candidate blocks according to PoW diff rules, in an entirely different location in the codebase, the code had been adjusted so that (all) candidate blocks were checked against PoS diff rules, hence the failure to match. I guess the Navcoin devs chose a different route.

I was able to route the candidate PoW blocks to the appropriate checks and get generatetoaddress working, hand-cranking (via a scheduled task) the PoW block generation phase. I have left Navcoin's staking schedule in place (because it has a 2hr minimum staking time whereas Bee has 7 days and I'm not hanging around for a week).

Anyway, staking does seem to be working ...



(The 50 BEE amounts aren't actually stakes, they are mislabelled PoW blocks.)

Also do you mean because we are trying to conduct this upgrade in the fairest way with this kind of auto balance shift to the new chain that it is proving to be much more complex than if we just forked nav coin and did a coin swap over to the new code base like that?

No, I was merely explaining the presence of a test premine in the committed code as “Plan B”. But having already performed some limited tests of the ledger transfer mechanism, I do have some justification for expecting “Plan A” to execute flawlessly.

But you might want to try it out for yourself. ATM, a candidate pre-release version of the Bee Core 0.13 network using a throwaway UTXO set is (thus far) happily ticking away on minkiz.co (our rented Hetzner box) and on two Linux laptops running locally (my new XPS with Mint 18.2 and my old Acer running Ubuntu 17.10).

I imagine most subscribers to this thread use Windows and am happy to report that (bar a couple of small tweaks) MXE cross-compilation of Windows binaries works out of the box  (https://minkiz.co/noodlings/bee/bee-qt.exe.zip), although I've not had chance to check its functioning on a Windows VM as yet. Edit: Windows users will need to set port=19999 in the config file, at least until I refresh the binary

Linux source code is available pro tem from: https://github.com/gjhiggins/been

It should just sync straight up. If not, addnode=144.76.64.49:19999

You should be able to check whether your imported BEE2 privkeys show any balance at all and if they do, whether they stake (2hrs minimum wait, atm). It's an elderly UTXO, when we're ready actually do the hard fork, I'll update it to reflect the distribution at that point and re-do entire the genesis block creation / PoW mining phase.

Cheers

Graham

[pass75]

Beetoshi 13.0.0 is online and working smoothly... so excited that I couldn't wait! 
Didn't tried yet to import my wallet privkey.
It seems a very good job.
Thank you very much Graham 

[pass75]

You should be able to check whether your imported BEE2 privkeys show any balance at all and if they do, whether they stake (2hrs minimum wait, atm). It's an elderly UTXO, when we're ready actually do the hard fork, I'll update it to reflect the distribution at that point and re-do entire the genesis block creation / PoW mining phase.

Cheers

Graham

I tried to import my wallet keys from my BeeCoinV2 wallet but there are no coins.
I used dumpwallet and importwallet commands.
Was I wrong?

[gjhiggins]

You should be able to check whether your imported BEE2 privkeys show any balance at all and if they do, whether they stake (2hrs minimum wait, atm). It's an elderly UTXO, when we're ready actually do the hard fork, I'll update it to reflect the distribution at that point and re-do entire the genesis block creation / PoW mining phase.

I tried to import my wallet keys from my BeeCoinV2 wallet but there are no coins.
I used dumpwallet and importwallet commands.
Was I wrong?

No, not wrong at all (I come from a different part of the universe, one where users are not referred to as “lusers”). Thanks for trying this out, it is hugely important to get feedback on actual use in the field, so to speak.

Could you try importing the individual BEE2 privkeys?

It may be because Bee Core 0.13 has native support for HD wallets. I don't know if it can import non-HD wallets from dumped from previous versions.

(Still hoping Plan A will work).

Cheers

Graham

[pass75]

You should be able to check whether your imported BEE2 privkeys show any balance at all and if they do, whether they stake (2hrs minimum wait, atm). It's an elderly UTXO, when we're ready actually do the hard fork, I'll update it to reflect the distribution at that point and re-do entire the genesis block creation / PoW mining phase.

I tried to import my wallet keys from my BeeCoinV2 wallet but there are no coins.
I used dumpwallet and importwallet commands.
Was I wrong?

No, not wrong at all (I come from a different part of the universe, one where users are not referred to as “lusers”). Thanks for trying this out, it is hugely important to get feedback on actual use in the field, so to speak.

Could you try importing the individual BEE2 privkeys?

It may be because Bee Core 0.13 has native support for HD wallets. I don't know if it can import non-HD wallets from dumped from previous versions.

(Still hoping Plan A will work).

Cheers

Graham

Okay, I tried to dumpprivkey 'my address' (the one on which i transfered all my coins when I moved to a new fresh wallet (read some post above)) and then importprivkey ***keys*** on the new BeeToshi but still balnace = 0.
After this I also tried a repairwallet but nothing to do... still no money 

[pass75]

Update:
Not knowing exactly when you made a fork of the old BeeCoinV2 to the new Bee and being my new address very recent (I moved all my coins approx 2 weeks ago) I though to try to import my previous old wallet.
After the rescan only one transaction jumped out 10/26/2017 of only 0.01097717 Bee (that came from staking) nothing else.
So balance 0.01097717. Very strange

[gjhiggins]

Update:
Not knowing exactly when you made a fork of the old BeeCoinV2 to the new Bee and being my new address very recent (I moved all my coins approx 2 weeks ago) I though to try to import my previous old wallet.
After the rescan only one transaction jumped out 10/26/2017 of only 0.01097717 Bee (that came from staking) nothing else.
So balance 0.01097717. Very strange

 Once again, heartfelt thanks for the feedback. What you describe is plausible. I'm in the process of updating the UTXO set, so your new addresses should show up in that.

It also occurs to me that the genesis block transactions which form the public ledger could be rephrased in a more accessible fashion by changing the transaction referents from pubkeys to addresses, i.e. change:

   txNew.vout[0].nValue = 10000000 * COIN;
    txNew.vout[0].scriptPubKey = CScript() << OP_DUP << OP_HASH160 << ParseHex("abee155f02a09bd70b498be5af25d7991703e404") << OP_EQUALVERIFY << OP_CHECKSIG;
    genesis.vtx.push_back(txNew);

to

   txNew.vout[0].nValue = 10000000 * COIN;
    txNew.vout[0].scriptPubKey = CScript() << OP_DUP << OP_HASH160 << ParseHex(DecodeBase58ToHex(std::string("3HN6ggDkexkUrHR7NNpgbhkBRY7eBckhMJ"))) << OP_EQUALVERIFY << OP_CHECKSIG;
    genesis.vtx.push_back(txNew);

Then people could just search the chainparams.cpp source for their address(es) and balance(s).

I'll make the switch when I re-generate the genesis block using the updated UTXO set. I'm just waiting for beecoinv2 to finish syncing before running the Python script that updates the UTXO database.

Cheers

Graham

[cryptohunter]

So really you are turning yourself into a fully skilled crypto developer.

It's not my intention. I'm a cognitive psychologist by discipline and a cognitive scientist by profession, the latter mainly defined by its use of computational models as investigative tools (hence my broad but patchy knowledge of programming / software engineering --- it was acquired pragmatically and in a piecemeal fashion). Although local constraints circumscribe my involvement to that of a hobbyist, if I had a professional interest as such, it would be in what you might be forgiven for thinking is a bit far-fetched but is very real and also very pertinent to altcoin communities: aspects of Theory of Mind as they pertain to collective intelligence.
https://phys.org/news/2015-06-intelligence-online.html
https://gfbertini.wordpress.com/2016/04/25/theory-of-mind-predicts-collective-intelligence-equally-well-online-and-face-to-face/

For convenience:

Have you ever wondered what factors may shape the interactions we have in online chatrooms? With the advent of the Internet 20+ years ago, the ways in which we communicate have drastically changed, allowing us to easily interact nonverbally or anonymously. Whether it's in a chatroom, email thread, or an online forum, most of us have taken part in some form of group communication on the Internet. Maybe, unbeknownst to us, we became a part of the group's collective intelligence, a form of group intelligence that can surface after collaboration and competition among individuals in the group. But some scientists are wondering, how can we measure the ability of others to communicate in a group, and how can we quantify the effectiveness of a group?

Two traits that make us "distinctly human" are our abilities to empathize and to interact well in social settings with others. These traits are usually measured in face-to-face situations, and may be more difficult to measure online, away from in-person social cues.

One factor that correlates to overall collective intelligence is "Theory of Mind" (ToM), or the ability of one individual to understand the mental state of another and recognize it as distinct from their own; what some may consider "mind reading." In a recent PLOS ONE study, MIT researchers tested the hypothesis that ToM, which can be used to predict collective intelligence in collaborative face-to-face tasks, can almost equally predict collective intelligence in online collaboration. One individual's ability to "read" the behavior of another individual can help contribute to successful communication and overall group intelligence. More than that, this ToM ability may exist even where verbal communication is prohibited, and may contribute to successful communication within an online group.

I'm applying an altcoin context to the questions: “how can we measure the ability of others to communicate in a group, and how can we quantify the effectiveness of a group”.

Except that I'm changing the question away from measurement and quantification to: “how can we best support ...”

Basically, my interest is in understanding the user task information requirements - what information is required to perform a specific task and how it should be presented to best support the process (of creating and maintaining accurate mental models of others).

Are there any specific questions ...

Unfortunately not. The Navcoin clone of Bitcoin Core 0.13 was an exercise in expediency, with parts of the code short-circuited in order to simplify the initial PoW phase - which I hadn't expected, so wasn't looking for.

It's because by the time Bitcoin Core 0.13 was released, the block generation part of the in-wallet miner had been completely obsoleted on mainnet by the shift to ASIC mining and the functionality/API had been adjusted to assume a testnet context with setgenerate (create blocks via continuous hashing) giving way to generate/generatetoaddress (create blocks on demand).

I tried the x11 miner without success and stopped at that point. So I'd had to use generatetoaddress to hand-crank the blockchain. What I hadn't spotted was that the API block generation code generated candidate blocks according to PoW diff rules, in an entirely different location in the codebase, the code had been adjusted so that (all) candidate blocks were checked against PoS diff rules, hence the failure to match. I guess the Navcoin devs chose a different route.

I was able to route the candidate PoW blocks to the appropriate checks and get generatetoaddress working, hand-cranking (via a scheduled task) the PoW block generation phase. I have left Navcoin's staking schedule in place (because it has a 2hr minimum staking time whereas Bee has 7 days and I'm not hanging around for a week).

Anyway, staking does seem to be working ...



(The 50 BEE amounts aren't actually stakes, they are mislabelled PoW blocks.)

Also do you mean because we are trying to conduct this upgrade in the fairest way with this kind of auto balance shift to the new chain that it is proving to be much more complex than if we just forked nav coin and did a coin swap over to the new code base like that?

No, I was merely explaining the presence of a test premine in the committed code as “Plan B”. But having already performed some limited tests of the ledger transfer mechanism, I do have some justification for expecting “Plan A” to execute flawlessly.

But you might want to try it out for yourself. ATM, a candidate pre-release version of the Bee Core 0.13 network using a throwaway UTXO set is (thus far) happily ticking away on minkiz.co (our rented Hetzner box) and on two Linux laptops running locally (my new XPS with Mint 18.2 and my old Acer running Ubuntu 17.10).

I imagine most subscribers to this thread use Windows and am happy to report that (bar a couple of small tweaks) MXE cross-compilation of Windows binaries works out of the box  (https://minkiz.co/noodlings/bee/bee-qt.exe.zip), although I've not had chance to check its functioning on a Windows VM as yet. Edit: Windows users will need to set port=19999 in the config file, at least until I refresh the binary

Linux source code is available pro tem from: https://github.com/gjhiggins/been

It should just sync straight up. If not, addnode=144.76.64.49:19999

You should be able to check whether your imported BEE2 privkeys show any balance at all and if they do, whether they stake (2hrs minimum wait, atm). It's an elderly UTXO, when we're ready actually do the hard fork, I'll update it to reflect the distribution at that point and re-do entire the genesis block creation / PoW mining phase.

Cheers

Graham

That's quite interesting and I do also find that the case in real life too. The more a person can chameleon himself to fit smoothly with another or for the best within a group of persons the more valuable they are. Even more so if the group is very varied in personality/ability types and they (the chameleons are like the oil that ensure least friction between the cogs. They are kind of like the interface that allows a connection between all parties. Extremely smart people often do not relate well to normal persons so their value (in a collective online effort) is not always as dominant as their iq would have you assume.


Great news on the new wallet I am going to download and test this out asap.

I have been sadly contemplating not having a lambo lately (since my crypto stash of value tumbled to more second hand older bmw levels) so not been so active on this board. But now i have spotted bee is springing to life again it will be great to help get it back on its feet.

I will ask if john can send out the mass message for beelievers to test the new bee wallet out.

thanks for your hard work graham. Although i don;t follow  what exactly is happening it seems obvious it is a time consuming and quite a nasty task to get all of this stuff working correctly.

[drax86]

I tried importing priv key and it shows 0 bee. also the syncing seems stuck on block 20000

[jolinahermosa25]

i would like to know more about this beecoin,any info about it,update us.i want to follow

[Neo.Prometheus]

I wish the progeny to be successful team. Every day more people will know more about the project. Good luck!

[nlrobbie]

I am not sure, did you swap those for beev2 in believe that swap was 2015-2016?
[/quote]

No

[cryptohunter]

I am not sure, did you swap those for beev2 in believe that swap was 2015-2016?

No
[/quote]

In this case it could now be impossible to switch

[cryptohunter]

how are ppl getting on with the latest bee client?

I have at last got bee 2 fully synced up now want to sync the latest client up but seems stuck on

Sun Feb 11

[drax86]

how are ppl getting on with the latest bee client?

I have at last got bee 2 fully synced up now want to sync the latest client up but seems stuck on

Sun Feb 11

Latest client so far seems stuck at block 20000 and no bee coins appear when importing key

[TheSea]

how are ppl getting on with the latest bee client?

I have at last got bee 2 fully synced up now want to sync the latest client up but seems stuck on

Sun Feb 11

Latest client so far seems stuck at block 20000 and no bee coins appear when importing key

Yes, I checked the new version of the wallet. I see an available balance, but probably staking does not work, so synchronization is stuck.

[cryptohunter]

how are ppl getting on with the latest bee client?

I have at last got bee 2 fully synced up now want to sync the latest client up but seems stuck on

Sun Feb 11

Latest client so far seems stuck at block 20000 and no bee coins appear when importing key

Yep same for me it stops at that block...  i didnt try the import because i was not sure it would work unless fully synced up

[anotherlateminer]

Is there any exchange that supports BEE?

[TheSea]

Is there any exchange that supports BEE?

At the moment there is no exchange. First we need to release a new wallet and synchronize a new chain of blocks.

[GREEDYJOHN]

Sorry for my absence - I have been too busy, too tired.

[drax86]

any new updates?

[cryptohunter]

has anyone got a fully synced bee (3) wallet and if so can you post some nodes?

[drax86]

has anyone got a fully synced bee (3) wallet and if so can you post some nodes?

I don't think there is a fully synced bee chain yet. I believe the 20000 blocks is all there is

[gjhiggins]

has anyone got a fully synced bee (3) wallet and if so can you post some nodes?

I don't think there is a fully synced bee chain yet. I believe the 20000 blocks is all there is

I set 20000 blocks as a trial, staking tx have to mature which means blocks have to be initially mined until the staking weight starts to support the network. PoS didn't kick in as I expected so I guess there's something that I don't yet properly understand but then again the network consisted of just three of my machines and PoS alcoins can get really cranky with small numbers of nodes. I need to look again at the code.

Cheers

Graham

[Real_Unhooked]

Any updates? When are we getting a new wallet? Seems to be ages ago? What is the hold up? Getting a bit impatient here if you can't tell

[cryptohunter]

has anyone got a fully synced bee (3) wallet and if so can you post some nodes?

I don't think there is a fully synced bee chain yet. I believe the 20000 blocks is all there is

I set 20000 blocks as a trial, staking tx have to mature which means blocks have to be initially mined until the staking weight starts to support the network. PoS didn't kick in as I expected so I guess there's something that I don't yet properly understand but then again the network consisted of just three of my machines and PoS alcoins can get really cranky with small numbers of nodes. I need to look again at the code.

Cheers

Graham

I did notice palmdetroit is back in the game and I did ask if he may be interested in helping out a bit. I think he said he had collaborated on a project with you before and maybe he can take a look at the pos side and see if he can see any bugs. I think he is familiar with pos from PHS.

Thanks for all you have done so far graham these things do take a lot more time and effort that people actually understand cbx is still getting their code straight  and have 2 devs on it. Good design and code takes a lot more effort and time than people sometimes understand..

Also next time if you announce ahead of time a date and time to start testing we will get a few community members to sync up and try to start pos off at the same time.

[drax86]

I can leave my bee wallet open, however when i imported my key, it still shows 0 bees so not sure if I would be any help to test staking

[pass75]

I can also do it if you need. Just let me know.
Thank you.

[gjhiggins]

has anyone got a fully synced bee (3) wallet and if so can you post some nodes?

I don't think there is a fully synced bee chain yet. I believe the 20000 blocks is all there is

I set 20000 blocks as a trial, staking tx have to mature which means blocks have to be initially mined until the staking weight starts to support the network. PoS didn't kick in as I expected so I guess there's something that I don't yet properly understand but then again the network consisted of just three of my machines and PoS alcoins can get really cranky with small numbers of nodes. I need to look again at the code.

Cheers

Graham

I did notice palmdetroit is back in the game and I did ask if he may be interested in helping out a bit. I think he said he had collaborated on a project with you before and maybe he can take a look at the pos side and see if he can see any bugs. I think he is familiar with pos from PHS.

Thanks for all you have done so far graham these things do take a lot more time and effort that people actually understand cbx is still getting their code straight  and have 2 devs on it. Good design and code takes a lot more effort and time than people sometimes understand..

Also next time if you announce ahead of time a date and time to start testing we will get a few community members to sync up and try to start pos off at the same time.

Because I don't have the resources to populate a peer-to-peer network to test it privately myself, I couldn't actually predict whether it would work at all. I offered it up so that people could, if they wished, see if their balance showed up correctly.

It would be great to be able get palmd's input, we last interacted a few years ago at the start of Spreadcoin - which is handy because as several other altcoin communities have found, devs are fairly reluctant to take on the responsibility for someone else's hacky code (and the Navcoin code itself is somewhat hacky).

I'm still looking into the source of the issue, the port is pretty much done and mostly working. I think it's a matter of ensuring that the configuration is internally consistent and coherent after the adjustment of the parameters to reference billions of coins rather than millions. I recently switched over to Helium for a couple of weeks to thrash out the details of their public ledger transfer and in the process, deepened my model sufficiently to be able to return to the Navcoin->Bee port with a much better understanding of what I might have got wrong. It was/is the next thing I was/am planning to do after attending to bitcointalk responses. I'll report back later this evening.

Cheers

Graham

[cryptohunter]

has anyone got a fully synced bee (3) wallet and if so can you post some nodes?

I don't think there is a fully synced bee chain yet. I believe the 20000 blocks is all there is

I set 20000 blocks as a trial, staking tx have to mature which means blocks have to be initially mined until the staking weight starts to support the network. PoS didn't kick in as I expected so I guess there's something that I don't yet properly understand but then again the network consisted of just three of my machines and PoS alcoins can get really cranky with small numbers of nodes. I need to look again at the code.

Cheers

Graham

I did notice palmdetroit is back in the game and I did ask if he may be interested in helping out a bit. I think he said he had collaborated on a project with you before and maybe he can take a look at the pos side and see if he can see any bugs. I think he is familiar with pos from PHS.

Thanks for all you have done so far graham these things do take a lot more time and effort that people actually understand cbx is still getting their code straight  and have 2 devs on it. Good design and code takes a lot more effort and time than people sometimes understand..

Also next time if you announce ahead of time a date and time to start testing we will get a few community members to sync up and try to start pos off at the same time.

Because I don't have the resources to populate a peer-to-peer network to test it privately myself, I couldn't actually predict whether it would work at all. I offered it up so that people could, if they wished, see if their balance showed up correctly.

It would be great to be able get palmd's input, we last interacted a few years ago at the start of Spreadcoin - which is handy because as several other altcoin communities have found, devs are fairly reluctant to take on the responsibility for someone else's hacky code (and the Navcoin code itself is somewhat hacky).

I'm still looking into the source of the issue, the port is pretty much done and mostly working. I think it's a matter of ensuring that the configuration is internally consistent and coherent after the adjustment of the parameters to reference billions of coins rather than millions. I recently switched over to Helium for a couple of weeks to thrash out the details of their public ledger transfer and in the process, deepened my model sufficiently to be able to return to the Navcoin->Bee port with a much better understanding of what I might have got wrong. It was/is the next thing I was/am planning to do after attending to bitcointalk responses. I'll report back later this evening.

Cheers

Graham

That all sounds quite encouraging. Thanks for the update on this Graham.

I hope that the community can all get ready to help test the next release on a certain date and time.

[gjhiggins]

I hope that the community can all get ready to help test the next release on a certain date and time.

I wish it were as simple as that.  I don't have the resources to create a model network to work with, so I cannot know whether PoS will work or not and so am hardly in a position to announce a test with all the false expectations that will inevitably arise.

anyway, in the interim, I made a few changes in a separate branch, named "rewind".  The ledger is now implemented as address-balance pairs: https://github.com/gjhiggins/been/blob/rewind/src/chainparams.cpp#L64 so now anyone can search for their Bee address in the list and check the balance. I re-cut the genesis block and reset the blockchain back to block 0.

https://github.com/gjhiggins/been/tree/rewind

The API generate call is functional - blocks are generated on demand. Bee privkeys should import and the balance should correctly appear. (It won't confirm unless you hand-crank the blockchain with generate).

Cheers

Graham

[gjhiggins]

(and the Navcoin code itself is somewhat hacky).

To wit, the line of code at https://github.com/NAVCoin/navcoin-core/blob/897ff05a9b4e5f248b32c4ede3a9c5dac6b88122/src/pow.cpp#L79 entirely bypasses the CheckProofOfWork calculation. Hard evidence of direct interference in the functioning of the engine.

Cheers

Graham

[drax86]

Importing Key appears to work now, doesn't show all my bee2 coins but that could just be based on when you forked the chain.

It appears that staking is working

[gjhiggins]

Importing Key appears to work now, doesn't show all my bee2 coins but that could just be based on when you forked the chain.

It appears that staking is working

Thanks for the feedback. I snapshotted the ledger a while ago, I'll update it so that folks' current keys work. Staking calculations do indeed seem to be working and that bodes well. However, the test addresses hat I used in the previous exercise did mature and were showing huge staking weight but when I stopped the script that was calling generate 1 every few minutes, so did the block generation. I have no experience of how the PoW->PoS transition works so I'll just have to build a model by working through the code than implements it. The situation isn't helped by the fact that the transition was implemented in the old 0.8.X navcoin and the 0.13 Core version may not even include that code.

Cheers

Graham

[dlsa]

this coins is dead 

[cryptohunter]

this coins is dead  

actually no  crypto can actually ever die. It is only ever resting awaiting a recall to action.

What you don't realise it that there are very very few real developers out there that can build and maintain an actual crypto currency. I mean understanding each part of it so they are in almost complete control.

That is why you see very few pos coins running on later builds. Most pos coins are just copy and paste of rat4 pos3 and if he decided to obfuscate any future bug fixes that arose they would all be ruined. Or if bugs popped up and he was not around to help fix then...

Graham is gradually learning each part of the code so in the end will actually be much more able to adapt and manipulate that code for any enhancements.

Beecoin is not dead it takes even fully trained (for years) crypto devs months and months to make adjustments and upgrades to their pos coins. For example cbx has two excellent devs one of which is the creator of posp (which is like pos3) and they have taken nearly over 6 months to enable new upgrades with masternodes and it is still not done. Regardless of which i am still confindent in that project too. These things take a lot of time to get correct.

However beecoin above any other coin i mined was the perfect POW launch and therefore I would feel comfortable saying it is the fairest of all the coins on this board. It would be fantastic to see it go further with micro tasks to enable all new crypto seekers a chance at becoming part of the community and I am confident given the unique position we are in with such a huge % of the minting to give away to new users either by staking that huge amount in staking/securing wallets (that could make us immune or less vulnerable to attacks that other pos coins are open to) and using all the pos interest to pay new community members to do micro tasks or fund all kinds of things.

I had previously assumed that i had lost more of my beecoins than i actually have so i will also be putting a lot of effort into reviving this project since i will not only be driven by the desire to see the fairest coins succeed but also because it will make financial sense for me too.

Not to sing my own praises but in the past coins that I have put a lot of effort into promoting have done rather well here, so to say this project is dead could not be further from the truth.

Our first major step will be getting on an exchange but actually i see lots of new exchanges and projects like rai got to be in the top ranks of CMC on some quite minor exchanges too. Also decentralised exchanges are on the up now too. So once we get to that stage we will certainly be back in the game.

I know many of you guys mined this and bought this whilst you could have mined and bought darkcoin etc which would have now made you millionaires. The same for me I was mining beecoin for months and months with all of my rigs because I assumed the fairest coins would be the last standing. This as yet could still be true.

beellionaires could still be possible

[drax86]

Looks like Staking is some what working without having to manually "generate' a block. I have a number of blocks that were staked up to an hour after my last generated block. There hasnt been anything for the last 3 days since then though

[drax86]

any new updates?

[rainbow7colours123]

Where can I get more information about this project, any websites or links?

[cryptohunter]

any new updates?

Graham is working on beecoin. I think it could take a bit more time as I think Graham is helping improve many good projects and is gaining knowledge from many different devs previous work.

Only Graham can give you a more detailed update but I am just telling you what I last heard and that was he was still working away on the beecoin port.

[supernva]

any news?

[Brooku]

It seems very amazing project for the future , maybe I can join as a team if you need , I can do as Indonesian translator especially the white paper or maybe as bounty manager.

[gjhiggins]

Uh, I found myelf replying to a post on the old thread and thought it would be better posted here ...

I can't believe how rude some people from the bee community can be after he has helped us all come back from nowhere.

People are just people, we all rely very heavily on simplified assumptions just to be able to get through life at all. Sometimes the assumptions are over-simplified and can lead the unwary into some entertainingly public flights of personal fantasy.

This PoW-PoS changeover thing is more challenging that it might appear. Take a PIVX port to Bee for example.

It's easy enough to clone the current well-developed version but the cloned code is working with an existing blockchain, the first 200000 blocks (ono) were PoW mined two years ago. Since then, no PoW mining has taken place on PIVX, the only reason for retaining the code is so that when a PIVX client syncs from the network, the integrity of those 200000 (ono) PoW blocks can be checked as they are received by the client.

If you track back in the PIVX bitcointalk thread to Aug 2016 (the beginning of the PoW/PoS changeover) and cross-reference that period with the PIVX github activity, you'll see about 6 upgrades released in the couple of weeks bracketing the PoW/PoS changeover.

For a PIVX-Bee upgrade, the situation is slightly different. PIVX (or DarkNet as it was called back then) actually needed the PoW period in order to effect the initial distribution. They arranged a changeover period when coins were minted using both PoW and PoS mechanisms, with the PoS stakeweight networkhash gradually taking over from the PoW mining networkhash under software control.

Bee already has a distribution, it just needs copying over to an upgraded client - which I've done.

The next task is to kickstart the blockchain, which involves persuading the (no longer functioning) PoW mining code to move the chain along until the disbursed Bee coins mature and start exerting sufficient stakeweight (according to the PoSv2 caculations) to cause mint-by-proof-of-stake to occur.

In case anyone's arrived late - in Bitcoin Core (i.e. > 0.9) there is a testnet facility to generate blocks on demand which I temporarily enabled for the Bee mainnet. I had to manually crank the handle in terms of a scheduled task calling generate 2 every minute in an attempt to mimic the Bee emission rate and get the PoS working in as-near-to-normal-running-conditions as I could. My simplified assumption was that re-running the code from block 0 would work. I failed to account for the possibility that the functionality of the PoW code would not be preserved by subsequent code developments - the rest of the code has moved on and no-one bothered upgrading the PoW miner because it wasn't used and now, because of changes elsewhere in the codebase, it no longer works. All that remains is the testnet facility for generating blocks on demand.

Well, that's how it was with Navcoin-as-Bee. Navcoin went through  the same PoW-PoS sequence as DarkNet, only earlier still. And, like Darknet, there was a hard fork at the point where everyone had to upgrade to the new (PoS-only) wallet.

I did have a public stab at it with Bee but it was a bit low-key because I was so uncertain about just how far my own simplifications had led me into a personal flight of fancy - that the PoS would "just" kick in because I couldn't see why it wouldn't. What I didn't (and still don't) know is how much stakeweight is required. It's possible that PoS would have taken over from the hand-cranked PoW if there was enough PoS nethash from staking clients. And it's also possible that the PoS would not have "just" kicked in for reasons of which I'm not yet aware. (Hey, I didn't write the code).

I'm experiencing much the same difficulty helping the Helium folks kickstart their PIVX clone. They're in a slightly more favourable situation in that the current Dash/Masternode axis is the result of independent development of a clone of Bitcoin Core 0.11 and still has the in-wallet miner (albeit in a decrepit state) whereas Navcoin is the result of a similar independent development of a clone of Bitcoin Core 0.13 - the one in which the upstream Bitcoin dev team decided to entirely remove the long-unused in-wallet PoW miner code, leaving just the on-demand testnet block generator.

So, there's no mining. Not without a lot of back-filling of old miner code which then needs to be brought up to date (with respect to all the other changes that have subsequently been made to the structure of the code) so that it mints PoW blocks once more. And then, after all that, disabling it again once the LAST_POW_BLOCK has been passed.

All in all, not exactly an attractive proposition, so I'm working on a means of circumventing it.

Does the miner work with an external miner? Good question. I don't know the answer because I'm on a laptop and thus far have had difficulty finding a CPU miner that can handle a post-0.10 protocol. I have one for OS X that might do the job (but I privately doubt it). I'm working on successfully compiling the OS X version of the Navcoin-as-Bee client so that I can find out whether it can still be mined by an external miner.

At worst, you'll need wait until Helium launches (cue hollow laughter) and then I can use that as a model.

Cheers

Graham

[htao]

Thank you Graham for the update, Much appreciated.

[794259332]

dead？

[gjhiggins]

dead？

Why do you ask?

[dutch_loneranger]

always love to read the progress you make or not make graham ,

if i read what you write i also learn about other coins and a little about blockchain and the problems and that is very intresting material too read

thank you for that and yes i also appreciate it very much and  i think many more even it is kind of silent here,

greetings ,

[gjhiggins]

even if it is kind of silent here,  

Fair comment.

I've been spending some time over in the Helium slack. Helium is a fork of PIVX with its public ledger transferred from Spreadcoin, so it is also a viable (if challenging) potential path for Bee. I've appointed myself describer and implementer of the public ledger transfer and I have worked out a scheme that uses the genesis block transaction to deposit the public ledger total into a multisig "Treasury" address (a notion directly transferrable to Bee). I need a functioning PoW period in order to test the Treasury multisig scripts that disburse the public ledger.

Like Navcoin, PIVX/Helium has an initial limited PoW period to allow staking coins to mature, ready for when the network staking weight has to take over from the PoW mining at the end of the PoW period. There are a number of other forks of PIVX, some of which have proved educational. I've recently successfully tested the basic PoW mining phase and the next iteration should test the PoW/PoS changeover - which, if successful, would position Helium pretty much ready for launch. And if unsuccessful, would position me for some further education.

Cheers

Graham

[TheSea]

https://chainz.cryptoid.info/bee2/#
Payment is exhausted. We will dream that GREEDYJOHN will pay again with his personal money?

[cryptohunter]

Fully operational long-term rental platform. It leverages blockchain technology to ensure seamless rental experience and allows for crowdsourcing to help tenants unfreeze millions of dollars tied up in rental security deposits.

ban the above account - some crazy bot spouting madness

[soopy452000]

Hello All,

How are you guys doing?

Warmest Regards,
˜SoopY˜

[kimtaek]

is BEE coins will rised again? Is there a possibility that this will have a bounty or airdrop from BEE coins?

[anotherlateminer]

Hello All,

How are you guys doing?

Warmest Regards,
˜SoopY˜

Doing well! BEE is a beast!

[TheSea]

Hello All,

How are you guys doing?

Warmest Regards,
˜SoopY˜

Life is Beautiful. We are moving to the highest heights of success and glory. Movement occurs in a spiral.

[QQ6693606]

where can trade

[anotherlateminer]

where can trade

Nowhere!

[pass75]

Hi guys, first of all Happy New Year to all the BeeCoiners!  
Then I want to say the blockchain seems to be stuck at block 2675634.
Can you confirm or is it just my sync problem?
My node (5.189.154.154) can see just 2 active connections and it seems both are blocked at 2675634.

getpeerinfo

[
{
"addr" : "1.34.180.245:1108",
"services" : "00000001",
"lastsend" : 1546934083,
"lastrecv" : 1546934075,
"conntime" : 1546934073,
"version" : 60015,
"subver" : "/TheHive:1.0.3/",
"inbound" : false,
"startingheight" : 2675634,
"banscore" : 0
},
{
"addr" : "144.76.64.49:1108",
"services" : "00000001",
"lastsend" : 1546934083,
"lastrecv" : 1546934079,
"conntime" : 1546934078,
"version" : 60015,
"subver" : "/TheHive:1.0.3/",
"inbound" : false,
"startingheight" : 2675634,
"banscore" : 0
}
]

[TheSea]

Hi guys, first of all Happy New Year to all the BeeCoiners!  
Then I want to say the blockchain seems to be stuck at block 2675634.
Can you confirm or is it just my sync problem?
My node (5.189.154.154) can see just 2 active connections and it seems both are blocked at 2675634.

I see that there are simply no nodes in the network to confirm the new blocks .. I try to synchronize my wallet.

[pass75]

I see you but it seems you are a lot behind
"startingheight" : 1288999,

I think it will need some days to complete the sync.
Anyway let us see what will happen

Thank you!

[CryptoSDesigner]

which Correct version Scrypt or X11 now ? please link to actual wallet or source 

[pass75]

It's just POS since long time.
Here is the link to the latest wallet
http://www.mediafire.com/file/0s200taomra572i/BeeCoinV2+1.0.3+Windows+Wallet.zip

[CryptoSDesigner]

It's just POS since long time.
Here is the link to the latest wallet
http://www.mediafire.com/file/0s200taomra572i/BeeCoinV2+1.0.3+Windows+Wallet.zip

any explorer and which now block ?

[TheSea]

any explorer and which now block ?

Block Explorer is currently unavailable ( https://chainz.cryptoid.info/# ).  I synchronized my wallet to block 2675680 and turned off staking.

[pass75]

It looks a bit better now: new blocks are generated even if very slowly (we are now at 2675681) and the blockchain seems to going on in some way
I think the staking is necessary for PoS to generate new blocks. So I restarted my wallet with staking enabled but it needs time to stake my coins.
Let us see what will happen. If I'm not wrong block time for BeeCoinV2 should be something like 30 or 60 seconds. Actually we are about 1 block per hour :-/

[pass75]

any explorer and which now block ?

Block Explorer is currently unavailable ( https://chainz.cryptoid.info/# ).  I synchronized my wallet to block 2675680 and turned off staking.

It will be very useful to restore the block explorer.
Does anybody know how to do it?

[TheSea]

any explorer and which now block ?

Block Explorer is currently unavailable ( https://chainz.cryptoid.info/# ).  I synchronized my wallet to block 2675680 and turned off staking.

It will be very useful to restore the block explorer.
Does anybody know how to do it?

https://bitcointalk.org/index.php?topic=571254.0
I do not remember the cost of use. This address is to receive payment for the use of block explorer for BEE COIN.
https://blockchain.info/address/19FvTou8RRg2mzcAXo27YoNxKSvBVg9pdN

[pass75]

any explorer and which now block ?

Block Explorer is currently unavailable ( https://chainz.cryptoid.info/# ).  I synchronized my wallet to block 2675680 and turned off staking.

It will be very useful to restore the block explorer.
Does anybody know how to do it?

https://bitcointalk.org/index.php?topic=571254.0
I do not remember the cost of use. This address is to receive payment for the use of block explorer for BEE COIN.
https://blockchain.info/address/19FvTou8RRg2mzcAXo27YoNxKSvBVg9pdN

Thank you!
I wrote to them. Let us see how much they will ask.

[soopy452000]

any explorer and which now block ?

Block Explorer is currently unavailable ( https://chainz.cryptoid.info/# ).  I synchronized my wallet to block 2675680 and turned off staking.

It will be very useful to restore the block explorer.
Does anybody know how to do it?

https://bitcointalk.org/index.php?topic=571254.0
I do not remember the cost of use. This address is to receive payment for the use of block explorer for BEE COIN.
https://blockchain.info/address/19FvTou8RRg2mzcAXo27YoNxKSvBVg9pdN

Thank you!
I wrote to them. Let us see how much they will ask.

Its 55 EUR for 6 months. I remember GREEDYJOHN paying it every 6 months back then.

[cryptohunter]

So I see a few people are getting back involved with beecoin. Let's hope we can get it going off the ground. The fairest POW launch of any coin period.

[pass75]

Re-enabling the stake on my wallet seems to have digged out the blocks generation from the stall. Now the time block seems to be again 30 seconds or so.
I don't know why I'm trying to keep this coin alive... maybe because it was one of my favourite ones, maybe for nostalgia...
But frankly speaking, with no money, no time, no dev, no people involved, no advs, its destiny seems to be already marked 

[dutch_loneranger]

Re-enabling the stake on my wallet seems to have digged out the blocks generation from the stall. Now the time block seems to be again 30 seconds or so.
I don't know why I'm trying to keep this coin alive... maybe because it was one of my favourite ones, maybe for nostalgia...
But frankly speaking, with no money, no time, no dev, no people involved, no advs, its destiny seems to be already marked 

you are not the only one that have this feeling some coins you just  have in your heart,
and have special feeling for it and  it is just a small thing too keep  a coin alive.
most important it is still alive and some have this feeling for it .

[QQ6693606]

still alive?

[cryptohunter]

I agree it is a shame.

I last heard graham was working on some parts of beecoin but that was some time ago so perhaps that did not work out as he hoped.

Time will tell. I still have some of my own beecoins and the community coins are still safe for a time in the future if beecoin kicks off again.

[Real_Unhooked]

We need someone to revive this coin

[pass75]

I'm keeping online one of the last 2 nodes out there since 2 years at least but it seems nobody is interested to re-launch this fair coin.
I'm sorry but I don't have the skills to do it.
I keep it alive because it was my first alt-coin mined.