[TESTNET]Bismuth - New Language, Interpretation Engines, DAPPs

[HCLivess]

Somebody is now spamming the network with the public post-geneis address, the fees seem to be getting paid correctly (around 4 bismuth per 1 bismuth transaction ) But that person is running an old client I think

My bad   I started from topic begining and tested all old clients)) btw new client getting in node windows some errors... but anyway i testet sending to myself and mining... But mining hard to understand because text is too fast ))

hi, I'm bumping up the network using the longest chain rule to fix sync issues
btw I need to add version checking, that's for sure

mining: if it's not on hold, it's ok

but the network has issues, I will need to deploy fixes to tx duplication

[1713996331]

1713996331

[1713996331]

1713996331

[1713996331]

1713996331

[1713996331]

1713996331

[1713996331]

1713996331

[adorid]

mostly in miner window i get text message: Reward status: Mined for this segment already

never mind, i figured out how its working

[MisO69]

Please remove all references to me and Vcash as we do not endorse, support or have any affiliation with this project.

References removed

Copyright infringement, Intellectual Property Theft, Illegal use of the Vcash trademark to promote the ICO scam (Bismuth). This matter has been handed off to Vcash attorneys.

You seriously banned me on your forum for endorsing your project, while calling mine a scam and an ICO? After I spent months on development and ideas while you secretly forked Peercoin? Why you must be sucha nut.. And you threatened me with a lawsuit? I even stopped posting there. I used to feel sad, guilty and inproper on your forum, now I just feel that you might be doing amphetamine derivates a little too much.
There goes my investing in VCASH I guess and the promotion and our Twitter love affair

From what I understand he plagiarized code without proper credit. Then he claimed the code was all his own. I think he is the one that's going to face a lawsuit. Anyhow, when I seen what he was doing with his launch of vanillacoin I completely lost trust in that individual.

[HCLivess]

Hi guys, here is a new release which fixes tx duplication which was a problem yesterday and today. I did some local testing and it worked, so let's try some testneting, please shut down your node before installing this version, as it contain an uncorrupted blockchain

https://github.com/hclivess/Bismuth/releases/tag/0.78

[MisO69]

Okay I have the new version up and running now.

miner is reporting that reward mined for this segment. Does that mean we need to make outputs/inputs to start mining on the next segment?

[HCLivess]

Okay I have the new version up and running now.

miner is reporting that reward mined for this segment. Does that mean we need to make outputs/inputs to start mining on the next segment?

yes, we need 50 blocks/transactions before new mining can be done. I have not seen your reward but after I deleted the transaction and had it synced from you, I can now see it (although nodes decide individually about rewards) I will keep an eye on the mining process

I can also see that the old transactions are being added from users whose nodes rolled back due to longest chain rule, huge success 

[adorid]

node is up and running

[MisO69]

Okay I have the new version up and running now.

miner is reporting that reward mined for this segment. Does that mean we need to make outputs/inputs to start mining on the next segment?

yes, we need 50 blocks/transactions before new mining can be done. I have not seen your reward but after I deleted the transaction and had it synced from you, I can now see it (although nodes decide individually about rewards) I will keep an eye on the mining process

So if I send you 10 bismuth 50 times or so we should see the miner kick in again and start mining? I'm gonna try this.

Yup - that worked. after 45 sends miner started again. I think I sent a few beforehand.

[adorid]

Okay I have the new version up and running now.

miner is reporting that reward mined for this segment. Does that mean we need to make outputs/inputs to start mining on the next segment?

yes, we need 50 blocks/transactions before new mining can be done. I have not seen your reward but after I deleted the transaction and had it synced from you, I can now see it (although nodes decide individually about rewards) I will keep an eye on the mining process

So if I send you 10 bismuth 50 times or so we should see the miner kick in again and start mining? I'm gonna try this.

the easiest way is to send yourself and some times need even 53 times before mining turning on))

[MisO69]

When the mining completed for that segment I had 1 bismuth sent to my wallet from myself again.

Seems like when your the first person to make an output on the new mining segment you get the reward for the set of 50 blocks.

[HCLivess]

When the mining completed for that segment I had 1 bismuth sent to my wallet from myself again.

Seems like when your the first person to make an output on the new mining segment you get the reward for the set of 50 blocks.

This is how mining works: If there is no reward in the previous 50 blocks, start finding a txhash of which the first three symbols match your address
If you find them before anyone else, you are rewarded with 25 bismuth



If someone produces 50 blocks in order to receive mining rewards before everyone else, they should pay extra on the fees. Max fee is around 5, 5x50 is 250, which is 10x more costs than reward. At least that's the intention

You should get the reward instantly after mining it, unless the a node with more blocks than you mined it also, in which case it will reject it

I started a testnet diary: https://github.com/hclivess/Bismuth/issues/11

[HCLivess]

Damn, got a negative fee and one missing block. Need to investigate.

Looks like some blocks got shuffled around way too much (old blocks from some nodes which rolled back are put at the end, therefore the timestamp difference is negative)

The missing block has returned, though  

[Charloz24]

I lost my bismuths with the latest update

[HCLivess]

I lost my bismuths with the latest update

Yes, there was some rollback, I am sending to all addresses now, thanks for reminding me

Also it seems that the QR code generator is working properly

[a3860903]

2016-06-29 11:52:06,875 <module>(60) Mempool: Reward status: Mined for this segm
ent already.
2016-06-29 11:52:16,878 <module>(60) Mempool: Reward status: Mined for this segm
ent already.
2016-06-29 11:52:26,881 <module>(60) Mempool: Reward status: Mined for this segm
ent already.
2016-06-29 11:52:36,882 <module>(60) Mempool: Reward status: Mined for this segm
ent already.

??

[bones261]

Also, some coins from the dev fund will go to Spoetnik and BitcoinEXpress for his long term contributions to this forum, that goes without saying.

You are joking here? Right? 

[adorid]

Damn, got a negative fee and one missing block. Need to investigate.

Looks like some blocks got shuffled around way too much (old blocks from some nodes which rolled back are put at the end, therefore the timestamp difference is negative)

The missing block has returned, though  

Manual refresh change fee and even with negative sign, i left mining all night, but didnt mined anything, its ok? ))

[Sylva]

Bismuth  python ,nice i will pay my attention on it

[HCLivess]

I opened up a slack since there are some devs who would like to help
I think I can add anyone if I receive their email address

https://bismuthdevs.slack.com/

[HCLivess]

Looks like I deleted adroid's latest post by accident. He asked about the jumping block issue (rollback crazy), I need to look into that