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

[HCLivess]

coins sent to both of your addresses
I will try to keep in mind to fix this non-balance mining issue

priorities :
make mining available without balance
fix rollback hack
introduce versioning into core

edit: fixed a bug which would not allow backed up transactions to be processed by passive nodes unless a new transaction is received (pushed/unreleased)

[1714138763]

1714138763

[1714138763]

1714138763

[1714138763]

1714138763

[1714138763]

1714138763

[1714138763]

1714138763

[kellendil]

coins sent to both of your addresses
I will try to keep in mind to fix this non-balance mining issue

priorities :
make mining available without balance
fix rollback hack
introduce versioning into core

edit: fixed a bug which would not allow backed up transactions to be processed by passive nodes unless a new transaction is received (pushed/unreleased)

when will you release the coin ? For real mining

[Qbanow]

Hi HClivess, I got this error every time  that I find a block and have to restart everything because the node stays stuck in the block found then my balance goes back to 10000 again. Any solution for this?

[HCLivess]

Hi HClivess, I got this error every time  that I find a block and have to restart everything because the node stays stuck in the block found then my balance goes back to 10000 again. Any solution for this?

Hello. Sorry, I introduced this bug when meddling around with consensus handling and have not released a fix yet (brb)
Also, there is a consensus persistency bug on disconnected peers which I will need to look into

[HCLivess]

coins sent to both of your addresses
I will try to keep in mind to fix this non-balance mining issue

priorities :
make mining available without balance
fix rollback hack
introduce versioning into core

edit: fixed a bug which would not allow backed up transactions to be processed by passive nodes unless a new transaction is received (pushed/unreleased)

when will you release the coin ? For real mining

Once I am happy with it, when there are no gamebreaking bugs. You can see the testnet diary here: https://github.com/hclivess/Bismuth/issues/11

[r.o.o.t]

Looks like an interesting experiment, if you need some help with linux stuff, let me know.
Godspeed

[raetsch]

anybody got this working on unix(ubuntu)?
i installed all mentioned dependencies and got the following executing gui.py

Code:

  File "gui.py", line 36, in <module>
    root.wm_iconbitmap(tempFile)
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1646, in wm_iconbitmap
    return self.tk.call('wm', 'iconbitmap', self._w, bitmap)
_tkinter.TclError: bitmap "icon.ico" not defined

Thank you for reporting this error, looks like the icon handling is incompatible with Linux-based system.
I updated https://github.com/hclivess/Bismuth/blob/master/gui.py with a workaround

Code:

import os
import os.name

if "posix" not in os.name:
    #icon

So the icon should no longer bother you in Ubuntu, please test and let me know if it works

yeah, gui is now running.
do i need to fill in the google-testnet-form for participating?

[HCLivess]

anybody got this working on unix(ubuntu)?
i installed all mentioned dependencies and got the following executing gui.py

Code:

  File "gui.py", line 36, in <module>
    root.wm_iconbitmap(tempFile)
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1646, in wm_iconbitmap
    return self.tk.call('wm', 'iconbitmap', self._w, bitmap)
_tkinter.TclError: bitmap "icon.ico" not defined

Thank you for reporting this error, looks like the icon handling is incompatible with Linux-based system.
I updated https://github.com/hclivess/Bismuth/blob/master/gui.py with a workaround

Code:

import os
import os.name

if "posix" not in os.name:
    #icon

So the icon should no longer bother you in Ubuntu, please test and let me know if it works

yeah, gui is now running.
do i need to fill in the google-testnet-form for participating?

Great
I would recommend everyone to fill the form in case we need to reboot the blockchain

[PGPpfKkx]

interesting. do you think Python is fast enough to handle a decentralized coin?

Also, maybe ask for help from the Python community? it should be difficult to pull this innovations alone.

Are you going to do an ICO maybe?

[HCLivess]

interesting. do you think Python is fast enough to handle a decentralized coin?

Also, maybe ask for help from the Python community? it should be difficult to pull this innovations alone.

Are you going to do an ICO maybe?

No ICO on the Bismuth blockchain, however there might be a Corporate fork in the future with a fine-sounding name and an ICO, fedora-redhat relationship with the Bismuth chain

The limiting factor for speed is the actual internet
I recommend reading this whitepaper http://www.activestate.com/white-papers/unveiling-origins-myths-use-and-benefits-dynamic-languages

Python community interest might be helpful, but I want to learn with this coin, as I have already learned a lot since the inception

[r.o.o.t]

I am no expert, but I think no amount of learning can overcome GIL

[frobley]

I've just run the latest version- this is on win7 machine, and receive lots of Errno 10060's -was running fine
could I have a coin for test mining? bd3681faa4b0f647416f9f649a1b6a883fb80c213088c655a945a871

2016-07-25 15:30:24,026 INFO worker(1352) Connection to 68.226.204.141:2829 terminated due to [Errno 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
2016-07-25 15:30:24,026 INFO worker(1352) Connection to 121.135.213.129:2829 terminated due to [Errno 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
2016-07-25 15:30:24,026 INFO worker(1353) ---thread <Thread(Thread-126, started 3720)> ended---
2016-07-25 15:30:24,026 INFO worker(1353) ---thread <Thread(Thread-122, started 3952)> ended---
2016-07-25 15:30:24,555 INFO worker(1352) Connection to 162.243.250.176:2829 terminated due to [Errno 10061] No connection could be made because the target machine actively refused it
2016-07-25 15:30:24,555 INFO worker(1353) ---thread <Thread(Thread-135, started 5744)> ended---
2016-07-25 15:30:25,023 INFO worker(1352) Connection to 133.130.112.228:2829 terminated due to [Errno 10061] No connection could be made because the target machine actively refused it
2016-07-25 15:30:25,023 INFO worker(1353) ---thread <Thread(Thread-133, started 5552)> ended---
2016-07-25 15:30:25,148 INFO worker(1352) Connection to 175.126.37.125:2829 terminated due to [Errno 10061] No connection could be made because the target machine actively refused it
2016-07-25 15:30:25,148 INFO worker(1353) ---thread <Thread(Thread-134, started 316)> ended---

[HCLivess]

https://github.com/hclivess/Bismuth/releases/tag/0.85
mining no longer requires you to have coins in this release, although old clients will reject such transactions ("fork")

[HCLivess]

I've just run the latest version- this is on win7 machine, and receive lots of Errno 10060's -was running fine
could I have a coin for test mining? bd3681faa4b0f647416f9f649a1b6a883fb80c213088c655a945a871

2016-07-25 15:30:24,026 INFO worker(1352) Connection to 68.226.204.141:2829 terminated due to [Errno 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
2016-07-25 15:30:24,026 INFO worker(1352) Connection to 121.135.213.129:2829 terminated due to [Errno 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
2016-07-25 15:30:24,026 INFO worker(1353) ---thread <Thread(Thread-126, started 3720)> ended---
2016-07-25 15:30:24,026 INFO worker(1353) ---thread <Thread(Thread-122, started 3952)> ended---
2016-07-25 15:30:24,555 INFO worker(1352) Connection to 162.243.250.176:2829 terminated due to [Errno 10061] No connection could be made because the target machine actively refused it
2016-07-25 15:30:24,555 INFO worker(1353) ---thread <Thread(Thread-135, started 5744)> ended---
2016-07-25 15:30:25,023 INFO worker(1352) Connection to 133.130.112.228:2829 terminated due to [Errno 10061] No connection could be made because the target machine actively refused it
2016-07-25 15:30:25,023 INFO worker(1353) ---thread <Thread(Thread-133, started 5552)> ended---
2016-07-25 15:30:25,148 INFO worker(1352) Connection to 175.126.37.125:2829 terminated due to [Errno 10061] No connection could be made because the target machine actively refused it
2016-07-25 15:30:25,148 INFO worker(1353) ---thread <Thread(Thread-134, started 316)> ended---

Hi, that's because we have many active nodes with forwarded ports, which are not online at the moment, if you want, you can manually open peers.txt and delete those nodes
you should still be able to connect to one at least (mine)

[frobley]

I've just run the latest version- this is on win7 machine, and receive lots of Errno 10060's -was running fine
could I have a coin for test mining? bd3681faa4b0f647416f9f649a1b6a883fb80c213088c655a945a871

2016-07-25 15:30:24,026 INFO worker(1352) Connection to 68.226.204.141:2829 terminated due to [Errno 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
2016-07-25 15:30:24,026 INFO worker(1352) Connection to 121.135.213.129:2829 terminated due to [Errno 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
2016-07-25 15:30:24,026 INFO worker(1353) ---thread <Thread(Thread-126, started 3720)> ended---
2016-07-25 15:30:24,026 INFO worker(1353) ---thread <Thread(Thread-122, started 3952)> ended---
2016-07-25 15:30:24,555 INFO worker(1352) Connection to 162.243.250.176:2829 terminated due to [Errno 10061] No connection could be made because the target machine actively refused it
2016-07-25 15:30:24,555 INFO worker(1353) ---thread <Thread(Thread-135, started 5744)> ended---
2016-07-25 15:30:25,023 INFO worker(1352) Connection to 133.130.112.228:2829 terminated due to [Errno 10061] No connection could be made because the target machine actively refused it
2016-07-25 15:30:25,023 INFO worker(1353) ---thread <Thread(Thread-133, started 5552)> ended---
2016-07-25 15:30:25,148 INFO worker(1352) Connection to 175.126.37.125:2829 terminated due to [Errno 10061] No connection could be made because the target machine actively refused it
2016-07-25 15:30:25,148 INFO worker(1353) ---thread <Thread(Thread-134, started 316)> ended---

Hi, that's because we have many active nodes with forwarded ports, which are not online at the moment, if you want, you can manually open peers.txt and delete those nodes
you should still be able to connect to one at least (mine)

I still have the error message for just the one node -
I've re-installed clean on another machine, checked tracert to 94.113.207.67, was ok few days ago 

2016-07-25 18:02:33,911 INFO manager(149) ---Starting a client thread <_MainThread(MainThread, started 2524)>---
2016-07-25 18:02:33,911 INFO manager(154) Only 0 connections active, resetting the try list
2016-07-25 18:02:33,911 INFO manager(157) Connection manager: Threads at 4/25
2016-07-25 18:02:33,911 INFO manager(158) Tried: []
2016-07-25 18:02:33,911 INFO manager(159) Current active pool: []
2016-07-25 18:02:33,911 INFO manager(160) Current connections: 0
2016-07-25 18:02:34,878 INFO worker(1353) Connection to 94.113.207.67:2829 terminated due to [Errno 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
2016-07-25 18:02:34,878 INFO worker(1354) ---thread <Thread(Thread-6, started 4816)> ended---

[HCLivess]

oops, my node was down, sorry

[frobley]

yeah working - didn't get to my wallet.. yet? though

2016-07-26 13:27:05,039 INFO <module>(104) Miner: Found a good txhash in 1248 attempts
2016-07-26 13:27:05,039 INFO <module>(108) Miner: Encoded Signature: u1ZFhtkXSD+DrgGGSSk0cllVzOTUulmrtMJMmvtUC7Nb5+iXO7xnFJyIShIX/F6FU1IIe54QrYiocskGxCAdkGQpsqPGV/fxIz2p+xdsqGBWn8Yshg0a5PXD9NnXTg64zUko2ihXud2YfAf5VsAOGDK4wFW+rm50LjLc3pJo1Rk=
2016-07-26 13:27:05,039 INFO <module>(114) Connected
2016-07-26 13:27:05,039 INFO <module>(116) Miner: Proceeding to submit mined block
2016-07-26 13:27:05,148 INFO <module>(125) Miner: Announcing 0000000576 length of transaction

I think we're all busy watching history being made, and many being given an education - what is forking? by demonstration.
It's friggin' great 

[HCLivess]

Yeah the ETC/ETH thing is insane  
my node got stuck on a lock for unknown reason, reset and now syncing - I sent it from "the other" node I think so after sync it should be OK

edit: you should have received your balance by now
there seems to be some issue, resolving

[HCLivess]

OK, I accidentally deleted some code with some other redundant code, making it impossible for nodes to sync

Here is a fix:

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

Expect some mining to be lost

[HCLivess]

CPU (0-12%) and memory consumption on Intel Atom