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

[davide72]

i would love to trie the testnet!

[HCLivess]

i would love to trie the testnet!

It is easy now with mining but I can send coins

[HCLivess]

https://github.com/hclivess/Bismuth/releases/tag/0.881
new version with exploit+mining fixes

[arielbit]

run node.exe
gui.exe

miner.exe seems stuck at

2016-08-01 11:30:45,256 <module>(62) Mempool: Reward status: Mined for this seg
ent already. One segment is 50 blocks long. You need to wait for those 50 block
 to pass before mining is available again. The miner will resume automatically.

[HCLivess]

run node.exe
gui.exe

miner.exe seems stuck at

2016-08-01 11:30:45,256 <module>(62) Mempool: Reward status: Mined for this seg
ent already. One segment is 50 blocks long. You need to wait for those 50 block
 to pass before mining is available again. The miner will resume automatically.

not stuck, but it doesnt spam the message now

[HCLivess]

I created a vanity address generator. You can pick what your address should start with and then attempt to generate it (I don't recommend going beyond 3-4 initial symbols)

https://github.com/hclivess/Bismuth/blob/master/vanity.py

Change

Code:

desired = "hcl"

[zorgn]

https://github.com/hclivess/Bismuth/releases/tag/0.881
new version with exploit+mining fixes

Well first, is there a 'clean' shutdown procedure to stop node.exe (Ctrl-C exception is catched) other than "kill -9" or equivalent?

I upgraded to the latest version, restarted everything and waited a while until the "Block Height" would stabilize (now 10299).
However since I restarted everything, I am missing a 25-bismuth reward (I had 3 before the upgrade, and now only have 2).
Is it because of the upgrade itself?

-Zorgn

[HCLivess]

https://github.com/hclivess/Bismuth/releases/tag/0.881
new version with exploit+mining fixes

Well first, is there a 'clean' shutdown procedure to stop node.exe (Ctrl-C exception is catched) other than "kill -9" or equivalent?

I upgraded to the latest version, restarted everything and waited a while until the "Block Height" would stabilize (now 10299).
However since I restarted everything, I am missing a 25-bismuth reward (I had 3 before the upgrade, and now only have 2).
Is it because of the upgrade itself?

-Zorgn

Interesting, please continue mining and tell me whether you get a new reward any time soon.
I would say this was caused by my emergency spamming and consequent reorganization (my blockchain was corrupted)
anyway, this should hopefully not happen anymore, there are failswitches now

[HCLivess]

Testing confirmations to prevent a "nothing at stake" rollback issue, active nodes get about 500 per block, passive about 50 with 5 minute blocks, anti-rollback is activated at 50 blocks
Will be released in the new version with an updated explorer
Confirmations are counted per block, not consecutively for older blocks (can be done separately, but I see no reason for it)

[HCLivess]

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

confirmations introduced
anti-rollback mechanism introduced
fees adjusted to prevent spam

[HCLivess]

I think we are nearing an official release for Bismuth, now that the main issues have been tackled (results still need to be verified). I would leave the testnet run for another few weeks, with serious stress tests, and then perheps release the mainnet. However, not sure about the DAPPS yet, whether they will be in 1.0 or added later.

[Dexter12]

Watching, looks like an interesting project.

[HCLivess]

Message signing and verification now work (will be released in an upcoming version)

[adorid]

What is chance to mine some block? because after 24h of mining nothing mined)))

[HCLivess]

What is chance to mine some block? because after 24h of mining nothing mined)))

If it takes you less than 128 seconds from start to finding a block, you will win a reward
Mining is available about every 4.19 hours with the current rate

latest winners:

6c59140a758bd8768e3a5d415e62c59c9c93e33778c55dd50b433952
911f15e9f0ea215f84ab9c550a16471ee013680b08c791936574fe88
f246e1b8d75e16e9451d6d8f22e63196c41ed26af7abd4f87fb3f44c
c5ada98e216c6b6525f82991d9b64daed394d9b40de69527662c1e08
7be4f0d6facd2d6125b2a32abc1a261f40e9455c78b0ac3a7e991dd9
bd3681faa4b0f647416f9f649a1b6a883fb80c213088c655a945a871

so it's pretty varied

http://94.113.207.67:5492

but people are not really sending any transactions now, so on mainnet mining might be a bit of a pain once it comes

[m4nki]

Interesting, will be following this.

[kahir]

HCLivess can the algorithm be more memory hungry to get rid of botnets .... like it uses at least 4 GB or more

[HCLivess]

Need to rework the tx engine

[raetsch]

How do I get this running on ubuntu?

install the dependencies
run node.py
run gui.py
run miner.py

[zorgn]

Hello,

looking at the result of "netstat" after leaving the node run for several days now, I notice that I have many connections with 94.113.207.67
Looks like a bug in the communication protocol? I would imagine a normal behavior would be to multiplex communications in 1 or 2 TCP streams?


  TCP    10.97.2.9:62086        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62241        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62242        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62244        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62256        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62259        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62262        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62263        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62265        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62267        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62268        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62274        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62278        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62292        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62293        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62294        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62295        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62296        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62350        58.173.246.16:8333     ESTABLISHED     4616
  TCP    10.97.2.9:62363        162.243.250.176:2829   ESTABLISHED     4988
  TCP    10.97.2.9:62434        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62437        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62438        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62440        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62445        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62457        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62463        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62466        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62475        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62479        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62500        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62548        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62550        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62551        94.113.207.67:2829     ESTABLISHED     4988
  TCP    10.97.2.9:62564        94.113.207.67:2829     ESTABLISHED     4988