nothing exciting to do, just run the new wallet instead of the old one.

but remember kids,
always make a back up if you want to keep your coins safe !!!

out of interest i pointed some hash at the pool
http://p2p.eternity-group.org/workers

currently there are two workers, i am the top one.
it's a rental quoted at 450mhs, and it's history during the rental looks pretty consistent.

ETtckQXQqjW2ccfMQT86LnM7SofNkfJF3G   43   0   100%   620.92 MH
EPqJCYbEiN4iFvwSfCWC2adNrgJNvBiMuv   10   0   100%   157.09 MH

there's some curious stuff going on

humorously i am consistently getting paid out less than the lower address.
it's certainly strange.



sample transactions
https://chainz.cryptoid.info/ent/tx.dws?207785.htm
https://chainz.cryptoid.info/ent/block.dws?156813.htm

if you havent sorted it join the slack for more assistance (invitation link in OP)

the problem is that while some users manage to have long-running masternodes, many others (myself included) find their master nodes going offline after some time.
there are some work arounds that are not too painful with some help.

and yes, the bug is present in a few other coins sharing similar code base and a search for a fix has been ongoing for some time.

i have recompiled it, and uploaded to releases

https://github.com/bumbacoin/Electra/releases/tag/v120



for whatever magical reason,
virustotal is currently giving this one 0 issues
https://www.virustotal.com/en/file/35732dcf3634e185519f51dcfac2c51a8cfedf28e6c60245eadf979bd3fd77b1/analysis/

to compare current uploaded file, notice
SHA256:   35732dcf3634e185519f51dcfac2c51a8cfedf28e6c60245eadf979bd3fd77b1

this checksum is unique to the file, should the file be changed in any way the checksum will change.
the recompile has changed it to create a new fingerprint.

lol.
i think we all enjoy a good dose of idiocy from time to time. thanks for todays clown action.

,
but apart from your amusing outlook,
you'll see above there are links to virustotal,
it lists kapersky as finding an issue.

crypto wallets have a long and glorious history of triggering virus scans.

there are no virus or otherwise nefarious inclusions in the wallet releases by me.

please feel free to behave in a manner which makes you feel safe,


..
edit,
earlier i checked virustotal report for prior release (v1121) and thought i found similar virus report,
however now it's clear with v1121 showing no issues..
i'm tired and no idea what i was looking at :p

there is very little difference between code bases so i have no idea why kapersky decided to flag this version and not the other.

i can try to re-compile it tomorrow to see if it comes up different, i dont see why, but given the minor differences in code that trigger this report,
perhaps recompiling it will actually change the outcome.

sorry my mistake,
this is the previous virustotal report on previous wallet v1121
https://www.virustotal.com/en/file/74fec486abd036835ea408074ed3330e3902feb9d3c9f16cd611ffef3ef349d3/analysis/1499266187/

it lists 1 issue as well.

i'm tired

edit
ffs now it's 0 issues. i really am tired :p my mistake

there should not be a trojan.
none were included

no idea why it's showing except for the generic long time issue of crypto coin wallets showing alerts due to the inbuilt miner.

..
here's the virustotal for previous wallet
https://www.virustotal.com/en/file/128e90867831def13e962c04097a3cf3ad4075aca2718568b606a017c94be237/analysis/

it shows the same result

dev wanted to be sure the chain was going smoothly before new exchanges, this update should fix a couple issues and be ready for moving up

new update available

FORK AT BLOCK 17100 - MANDATORY UPDATE

https://github.com/bumbacoin/Electra/releases


this update fixes PoS reward,
and also reduces 432 block confirms for coinbase rewards.


block 17100 is in roughly 1 week time so please update
mac update to come soon

we're working on that now,
the issue has been identified but it will require another fork,

and because of the necessity of a fork we're just making sure this one will be the last one.

out of interest i thought i'd go and have a look at the first few blocks (the alleged instamine),
unfortunately the working explorer doesnt allow you to follow outgoing transactions  :p

as each of the early blocks are all different addresses,
it does look like the code base uses unique addresses for each PoW block.

at this point though it works out 4338 of the current 145000 were mined before any one posted stats here..
which is around 3% of current supply.
not a huge amount after a bit more than 3 months after release.


..

from post above coinexchange.io also only has something similar, i'm guessing they get their data from coinmarketcap
Available Supply   68306.00000000 HONEY

i'm still getting used to your new model explorers


i'd like to make a couple of suggestions

- make them searchable by height.
i had to click on a block, then change value in teh address bar,
not difficult, but not user friendly

- show outgoing transactions from addresses
one of the main purposes of bitcoin is to have a fully readable transaction history,
which also includes outgoing transactions against an address.

its obviously all about the magic of the bumba

i've sent the dev a PM regarding strange PoS payouts,

it seems a strange issue of code ordering, it looks fine but behaves as we see.
basically atm the expected reward is divided by 1000000

fixing it will require adjusting how the code works out stake rewards so it will need another fork.

.
a slight note in regard to how reward is calculated,
the min stake age is deducted from reward calculations,
so a payout after two days would be worked out minus 24 hours (min stake age), => payout would then be based on 1 day.

for a coin with over 630 billion coins 0.01 is a tiny fee. lol

but you can experiment with changing the tx fee by going into debug/console

We're in full PoS now.

from the OP, 50% rewards.

honey wallet on coinexchange.io seems back up.

with lack of any other information, i assume v1040 is still the version of choice.
looking forward to the update

ah yes, sorry about the confusion.
i've re-worded the readme to hopefully help allay future confusions.

i created this fork in response to a bounty the TorCoin developer offered (not that the developer has been seen since )

whilst it is a fork of the code, it is not a network fork.
the only difference being how the clients connect to the TorCoin network.

the original connect to each directly and find peers through hardcoded nodes and irc,
the tor integrated version uses the Tor network and connects to hardcoded nodes.

have a look here,
https://github.com/bumbacoin/stronghands/releases
a while ago there was an issue with sending too many coins = breaking yr wallet,
so i did a small fix and compiled new versions


the explorer is taking a long while to sync ... only half way and been at it for quite some time ..
it's here, still needs a little tweaking but i'm waiting till it finishes syncing
http://173.254.204.74:3001

crashes can often corrupt database.

if it keeps doing that
you'll need to delete your copy of the chain and restart.

make sure you keep your wallet safe