I need a set release date or I'll never focus on core stability before extending functionalities 
Scope Creep!!
Yeah, it's a form of reward/escape
Sadly, fixing bugs takes longer than adding new features
Maybe we must learn to love fixing bugs
Topic: [TESTNET]Bismuth - New Language, Interpretation Engines, DAPPs - page 2. (Read 49741 times)
Scope Creep!!
Yeah, it's a form of reward/escape
Sadly, fixing bugs takes longer than adding new features
Maybe we must learn to love fixing bugs
I need a set release date or I'll never focus on core stability before extending functionalities
Scope Creep!!
Yeah, it's a form of reward/escape
Sadly, fixing bugs takes longer than adding new features
I need a set release date or I'll never focus on core stability before extending functionalities
Scope Creep!!
I need a set release date or I'll never focus on core stability before extending functionalities
Speaking of bugs
https://github.com/hclivess/Bismuth/releases/tag/2.59
Speaking of bugs
https://github.com/hclivess/Bismuth/releases/tag/2.59
Code:
Increased timeouts
Fixed mempool merging with both empty and full mempools
Added support for mined transaction display in GUI
Improved mempool logging
Fixed mempool merging with both empty and full mempools
Added support for mined transaction display in GUI
Improved mempool logging
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
Don't rush it, its better to have something stable than a buggy release.
When mining is it normal for the GUI to show 0.00000000 as the amount mined?
If it is normal why?
Thanks
Conscripted
If it is normal why?
Thanks
Conscripted
Hi, reward has it's own special field in the database, it is not the same as "received"
I'll try to fix it in GUI, I understand it's confusing
https://github.com/hclivess/Bismuth/releases/tag/2.58
Troubleshooting those hanging nodes, this might help
Troubleshooting those hanging nodes, this might help
Fixed reintroduction of missing exclusivity for block digestion, which caused block corruption and rejected blocks
Changed the OpenField to TEXT, adjusted logo placement
Block digestion reorganization
Block digestion error message fix
https://github.com/hclivess/Bismuth/releases/tag/2.57
Code:
Moved back block info fetching to appropriate location
(Fixed error where sync would take diff from the first block during massive sync)
(Fixed error where sync would take diff from the first block during massive sync)
Hi, had some issues with new code, so here's reconsolidation:
https://github.com/hclivess/Bismuth/releases/tag/2.562
* Bismuth can handle hundreads of transactions per second
* The colors are Bismuth colors
https://github.com/hclivess/Bismuth/releases/tag/2.562
* Bismuth can handle hundreads of transactions per second
* The colors are Bismuth colors
I like the website info. But acid color design is a bit ambiguous.
Could it be problem that i make a lot of transactions to myself?
Hi, blockchain is stuck, around line 337 we need some changes, fix probably coming later today
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
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
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.
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.
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
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.
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...
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
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...
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...
Feel free to test the new version
https://github.com/hclivess/Bismuth/releases/tag/2.25
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
Jump to: