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

[gawlea]

I would like to boast about hyperblocks a little. Since I've read up this by Gavin http://gavinandresen.ninja/utxo-uhoh, I now know that unlike Bitcoin, Bismuth has no UTXO problems, because it uses a different approach. Another advantage is that Bismuth "light" nodes have the same functionality as Bitcoin full nodes and can confirm transactions without hassle.

I like the title HCLivess 1000% new

[maccaspacca]

Bismuth Tools now updated and published in new repository

https://github.com/maccaspacca/BismuthTools

For the moment I am only publishing a desktop version

future releases may have (depending on time and core code changes)

1. Better menus and help system
2. More wallet features and possibly node and miner functions
3. Network information
4. Logging features

[HCLivess]

Thanks for the hard work, maccaspacca.

I am reconsidering the launch of Clarity, because one chain will be quite a lot to handle on it's own. One of the community members suggested we do the dev rewards instead, so I opened a poll for that. This would mean there would be some premine to reward community members and testers.

[eule]

This looks interesting indeed, what is the limit of user data to be stored in one tx and in one block?

[maccaspacca]

Bismuth Tools 0.2 released

https://github.com/maccaspacca/BismuthTools/releases

[HCLivess]

This looks interesting indeed, what is the limit of user data to be stored in one tx and in one block?

For now there is no limit, but data is enforced by increased fees. Some testing would be valuable on long OpenField entries, feel free to test the testnet
62 kb (http://www.sacred-texts.com/dna/hgp011k.htm) costs 135 Bismuth to send now




Also, everyone please notice there is a new version which we successfully troubleshot yesterday.

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

Code:

Please DELETE your mempool.db
New testnet version 7002
Restored proper signature validation
Minor adjustments to GUI and Miner user experience
New database column: "keep" replaced "confirmations", it is used to prevent pruning of some txs
GUI now has a "keep" switch
Hyperblocks now tolerate non-prunable transactions (needs testing)
Fixes to denominations
-- Node to node sync fixed
-- Digest fx fixed

[HCLivess]

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

- Quicker start
- Tor support
- To use tor, download Tor expert bundle (Win: https://www.torproject.org/dist/torbrowser/6.5.1/tor-win32-0.2.9.10.zip) and run tor.exe
  Then you need to enable tor on the last line of config.txt (change "tor=0" to "tor=1"). Then run node.exe

Ninja patch for passive nodes from 2.23, used old module which had functions messed up

[kakaxibkl]

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

- Quicker start
- Tor support
- To use tor, download Tor expert bundle (Win: https://www.torproject.org/dist/torbrowser/6.5.1/tor-win32-0.2.9.10.zip) and run tor.exe
  Then you need to enable tor on the last line of config.txt (change "tor=0" to "tor=1"). Then run node.exe

Ninja patch for passive nodes from 2.23, used old module which had functions messed up

The previous BUG back,
Every other time the wallet will disconnect from the network
Do not regularly restart Start Node wallet will synchronize

[HCLivess]

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

- Quicker start
- Tor support
- To use tor, download Tor expert bundle (Win: https://www.torproject.org/dist/torbrowser/6.5.1/tor-win32-0.2.9.10.zip) and run tor.exe
  Then you need to enable tor on the last line of config.txt (change "tor=0" to "tor=1"). Then run node.exe

Ninja patch for passive nodes from 2.23, used old module which had functions messed up

The previous BUG back,
Every other time the wallet will disconnect from the network
Do not regularly restart Start Node wallet will synchronize

Please upload your node.log to http://pastebin.ubuntu.com and send the link. Also make sure to delete any socks.pyc or socks.py in your folder if you are not using the installer/exe

There will be no direct transfer of funds from the testnet to mainnet, but there will be reward tiers, probably paid from the development fund

I advise you look and try to find the following in the log: Threads at 70/75

[adorid]

I have the same problem, network shows behind and one moment up to date... Mined balance disappears after some time and in node logs i can see that "Could not connect to ip address:2829"
Btw maybe is good to disable mining while wallet syncronizing

[HCLivess]

It seems that a person with IP 62.63.136.166 / f34361fe61a9a7aacaac839472e999f39602f82d543316e2a6744dd0 has desynced clock and is mining with future timestamp. Can you comment on this, please?
But I was able to optimize the node sorting procedure / banlist It still could be an issue in coding, that's why I'm asking to share details

Code:

2017-03-30 15:30:07,806 digest_block(744) Incoming: Valid signature
2017-03-30 15:30:07,806 digest_block(754) Digest: Future transaction not allowed, timestamp 1365.31866667 minutes in the future
2017-03-30 15:30:07,855 handle(1089) Incoming: Received: mempool from 127.0.0.1

[HCLivess]

Feel free to test the new version

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

Code:

Dropped "onefile" compilation for compatibility reasons
"Run as administrator" is no longer required
Rewrote the compilation script
Disabled future transactions in mempool
Changed display of values in GUI and prevented rounding (old request)
Changed banlist to prevent it from crashing the node / overfilling threads (basic testing done)
Added details to some logging

[adorid]

Yea thats me with clock problem i changed clock time to real.

Simply was wrong computer time with launched wallet.

Btw new version node cmd windows opens and after some time closing by itself...

[HCLivess]

Yea thats me with clock problem i changed clock time to real.

Simply was wrong computer time with launched wallet.

Btw new version node cmd windows opens and after some time closing by itself...

Thanks for testing, I am intensively changing the mining algorithm at the moment so a new release is every few hours, we are testing in various mining environments. I recommend checking back in a day or two for the new version

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

This should fix the crashes

[Xenophanes0]

Is the main net coming soon?

dev is off till early March, so will be months till mainnet launch. Cheers!
P.S. you can always give a hand on testnet

mainnet will be better step to launch especially for new users.

[HCLivess]

Is the main net coming soon?

dev is off till early March, so will be months till mainnet launch. Cheers!
P.S. you can always give a hand on testnet

mainnet will be better step to launch especially for new users.

Hi, here's a release statement, I hope for very early April, but want a healthy network

http://bismuth.cz/launch/


currently testing a patch for the passive node disconnection after several hours, release tomorrow if node doesnt die overnight

[maccaspacca]

Bismuth Tools 0.40 release

https://github.com/maccaspacca/BismuthTools/releases/tag/v0.40

Fixes following recent Bismuth client changes and other code fixes

Linux included for experimental / future use.

[HCLivess]

This version of Bismuth goes with that version of Bismuth Tools

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

Bismuth hard fork to include nonce mechanism in mining to prevent potential incentivization of blockchain timestamp alteration. I have a multithreaded miner ready and will release it with the upcoming version. Also stability issues for nodes seem resolved (still testing). The last one thing planned before the mainnet is the names registration (aliases), which are already supported in the Bismuth Tools - no forking required for that one, so we might as well keep it for after launch

[HCLivess]

There's an announcement I forgot to make, we now have an official website:

http://bismuth.cz/

[HCLivess]

Hi, blockchain is stuck, around line 337 we need some changes, fix probably coming later today