To let the community know.

I have sponsored the node and block explorer @ Cryptocoinexplorer for the next year in hope that it can be continued to be used as a tool for the bitbar community. The Explorer is run by Dreamwatcher, a respected member of the crypto community whos dedication and experience speak for itself.

Through my correspondences with Dreamwatcher, I shared updates on the status of Bitbar...

The Bitbardev going offline (leaving the project?)

Mullicks involvement I'm early 2015,

The lack of any dedicated Developer/coder on the project at this time.

I reached out to Dreamwatcher about potentially working on Bitbar after hearing the outcry for development from the community. I figured he would be a logical choice in heading up the project after his original coding of CCE,  his work on multiple types of crypto-currencies of the star trek theme, and the online exchange of said cryptos.

I feel like we are at a stage where with the proper Coding Developer, and the dedication of community involvement, we can turn the tide on Bitbar, and be proud of having taken part in doing so.

With the renewal of CCE for 2016, Dreamwatcher has expressed interest in further development of bitbar, as a Dev . We need a proper developer.

I'm sure he will weigh in here, as he has in the past. But the prospect of this becoming a reality drove me to inform the community now.

I welcome any opinions and support for this move forward.

Spiderboxes advise is a good way to go. I would say keep your wallet up, when you sync if your bars are still unconfirmed copy the received address and go to the console, dumpprivkey and save it. Back up the wallet and save it to some sort of digital medium (the private key can be saved on paper)

Depending on what chain the exchanges sync to, the bars may confirm or turn to orphan blocks.

I would then make a fresh wallet knowing that I have those potential bars backed up, for the fact that I would not want that constant reminder when I look at the qt client.

Ultimately the decision is yours, but having a wallet online and synced is a big help to everyone in terms of connectivity.

The safest answer I can give you is to backup the addresses you received coins to, perhaps a paper wallet or of the wallet.dat file and come back to it in the future after everyone is on the same chain.

I am on the longest chain, connected to the oldest node but things are not certain even for that.

It sucks, but thus isn't the first time anyone has lost due to split chains.

I myself have been a victim of pools going rouge in the past (anyone remember diggers pool?)

until there is more infrastructure surrounding bitbar all we can do is try to help eachother out by spreading information.

Speaking of, I am excited to share some information concerning possible future developments....

more to come

I received a message from Mastermining that he would be syncing his pool to the explorer at Cryptocoinexplorer.

It looks like he failed to sync, as I saw a message on the site about it. I have isolated my node and will transmit it to him again to hopefully get things straight over there.

Another thing is when syncing, one can use the command

connect=68.191.93.33 in the bitbar conf file to lock onto my node and sync.

I am running a full node synced with Cryptocoinexplorer, Block count 142596

addnode=68.191.93.33

CCE runs a dedicated node @

addnode=btb.altcointech.net

Hope this helps

What an interesting development...

There are 3 different blockchains...

Cryptocoinexplorer

Mastermining

Ispace.co

Each are mining their own chain.

Cryptsy & Bter wallets down, yet trading resumes.

Apparently a new Dev taking over, 5mil, affiliated with cryptsy some how.

And Bitbar.co becoming a resource/home page.



I personally would like to 5mil to weigh in, let the community know any plans. I would hope that he/she would make it priority one getting the wallet back up at Cryptsy, and consolidating these rouge chains

Its the reward that has to exceed 0.0099xx in order to be added to the output.

POS Difficulty is less than 0 right now, so low tx are creating blocks with no/rounded down to 0 rewards.

I mentioned varying 5% interest rate in an earlier post meaning as POS difficulty rises, that minimum transaction block that would generate a reward @ full maturity (90 days) may not immediately stake a block and reward having to compete with other stakeholders and an increasing difficulty.

It may indeed take another day, week, month ect. of being open and ready to stake before the block is produced if difficulty dictates, and thus interest would diminish according on the extra time beyond full maturity. (90 days)

The example I gave above shows a block size close to 10BTB will produce interest after 1 month.

We could speculate that a tx worth 3.33BTB might also skate interest after a 3 month period, but would need to experiment to find out.

This is correct.

You will incur a transaction fee sending yourself the full amount, the fee varying depending on the size, but probably between 0.001 & 0.004 destroyed.

Remember Bitbar is an inflationary/deflationary currency, having tx fees destroyed along with POSrewards gained.

When you send yourself 49.7btb, after 30 days the block will want to stake into to two transactions equaling  theoriginal total + 5% annual interest.  

Would look like  49.7 -> 24.95
                                      -> 24.95  based on 30 day value, a gain of 0.20 btb respectivly, 0.10 per tx.

If you waited the full three months it would look like


If you waited any length of time afterward, say one year later, it would still look like


49.7  -> 50.32125 because after 90days the POS reward does not continue to grow

Feel free to use the info to update bitbar.co

I have learned this by reading posts, studying the blockchain, and some experimenting too.

I am in contact with Mastermining and he is awair of the multi chain issue. He can sync his pool back to CCE if its determined to be a valid chain.

But first Cryptsy needs to get their wallet synced and up to date. If 5mil is affiliated with cryptsy, I would hope he can work thus issue out and get us back up and running on the exchange.


I noticed ispace.co shows they are mining blocks to a
Wallet Version: v0.4.0-nvc-8-g30741b0-dirty-beta

That sounds kinda shady to me... just sayin

http://btb.cryptocoinexplorer.com/ is a sponsored block explorer that has been active since 2013. Part of the sponsorship includes a dedicated node that can be connected to @ btb.alcoin.net

I have connected to this node and am  accepting blocks through my wallet.


There is a minimum amount to stake to get rewards in the current code.
Your POS blocks are indeed moving the network along by confirming transactions but if they are small amount, they will not get a reward.

As we know Proof of Stake is a concept Bitbar adopted from peercoin, which gives the currency a variable inflation rate, but also an energy efficient property by allowing holders of the currency to generate blocks for much less energy required by miners. Apparently there was a block reward De-synchronization issue that was noticed and fixed in Bitbar by the Developer of peercoin, Sunny King. This is why currently small rewards are rounded down.
tbar
Rewards also depend on Coin age of transactions. Every transaction is eligible for POS after 30 days, and up to 90 days. If a transaction is left untouched for 30 days, it will begin to try and stake a block on the network. If it stakes at this point, the transaction will split into two smaller equal outputs totaling the initial stake amount.

Take a look on the block explorer here http://btb.cryptocoinexplorer.com/address?address=BJTuq5JSLzRbZyw8xurtYejt5Q4cur8rcq

Notice the transactions that "split" into 9.475BTB from 18.9. They staked after 30ish days and gained a total reward of 0.05 bitbar, very close to the annual .05% inflation rate in the bitbar code.

If one were to not touch the transaction for 90days, it would be considered fully Mature and when it stakes, it would not split into two transactions, and the reward, if eligible, would be added to the original transaction.

Once the transaction is older than 90 days it does gain extra coin age, the the proof of stake reward will not grow past the 90 day full maturity level.

I want to say 4-5BTB would be required at full maturity to stake interest at this time.

Proof of stake difficulty is so low on the network that mined blocks Les than 1btb are staking very easily.

If you want rewards, you will have to combine your mined blocks into a large enough transaction meeting the criteria above to gain reward.
Hope this helps,

Cryptsy wallet is down @ 135775 Blockheight

http://ispace.co.uk

http://btb.mastermining.net

The two current Bitbar pools are different Blockheights around 141xxx.

Both pools block explorer points back to http://btb.cryptocoinexplorer.com/ however ispace.co does not match the explorer.

Mastermining matches until today, now the explorer is showing a large amount pos blocks coming in 100+ blocks higher that your pool.

There is awallet is loaded with mined blocks that are proof of staking at a high rate due to Low PoS difficulty of the network.

I might rethink that decision honestly.

I'm working on a post do give me some time please to explain my position.

A status update,

As of 10/20/15 Bitbar wallet is still in maintenance mode at cryptsy. I opened a support ticket, and haven't heard back from them as of yet. I sent Mullick a PM here describing the situation as well, and for some possible input/insight but have not gotten a response.

Crypto coin Explorer block Explorer is still connected to at least 9 peers, and still processing blocks. It may be that they are on a correct chain, if in fact cryptsy isn't on a rouge chain as we may suspect. For now, Dreamwatcher will continue to monitor the current chain being monitored at CCExplorer, until definite word/ conclusion can be ascertained from cryptsy.

I also set up an account with Mintsy, which offers dedicated mining contracts. I I am uncertain if they offer mining support for Bitbar, but have contacted their support to see if that is a possibility. I was entertaining the idea of perhaps a Mining contract in order to have dedicated hash power on the chain, to help prevent situations that we may be encountering at the moment. this may be accomplished through crowdfunding, if we can garner the support.

more to come

The research I conducted left more broken links, and non-support for Bitbar.

Out of the nine or ten pools that have mined BTB once, the only one left working is mastermining...

Their hash rate has decreased significantly, to about 1.5 mh.

This leads me to conclude that there is an entity out there with more hashing power than the entire network being monitored by Cryptocoinexplorer.com and mined by mastermining.

Basically they are solo mining the chain, the chain that Cryptsy seems to be accepting.

If they say, (cryptsy) they they have confirmed that bitbar has been sent to your account, I would take the address you gave them, dump the private Key in your Qt client, and save it somewhere with the arbitrary amount they say is assigned to that address.

I'm going to email Dreamwatcher @ CCE and let him know his block explorer is not being used, or isn't current with cryptsy.

Mastermining really needs to be notified as well... but here's the slippery slope.

When they (MM) take their pool down for maintenance, there will be no public pools mining Bitbar.

None. (At least from what I gather)

edit: Ispace.co.uk was mining btb with their pool at this time...

I  used cgminer to solo mine bitbar. There is a tutorial still available on this site.

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

I made this work on a windows machine, I am unsure of the steps involved to solomine linux.

I believe it is 6% annual

to simulate real world inflation rate

As of now smaller amounts that stake create blocks that advance transactions, but create no interest.

Proof of Stake blocks are eligible after 30 days, and can take longer depending on the amount being staked.

For maximum stake, one must wait 90days.

Also wallet cannot be locked.

Yes, the repository on github is on mullicks name since he added checkpoint after accidental fork earlier this year.