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

[HCLivess]

OK, I added an exclusive mode on every network function which uses the database, let's see how that works

New release + mining should be available again (or soon)
https://github.com/hclivess/Bismuth/releases/tag/0.83
issues mainly concern(ed) active nodes (me)

This might be the last attempt before reworking the whole thing into two separate lockable mempools, which might impact performance

[Qbanow]

Hi, interesting project. Could someone send me a few coins to this wallet: f1f1594aafa9ebda5e1e0aa09af8d0d3ff324ea793c0d1d87bcd28d2  I would like to play with mining option. Thanks in advance. I'll stay around getting fresh news and giving support to the testnet.

[HCLivess]

I can see two mining attempts which were rejected due to chain reorganization



or perhaps these are normal transactions

so far no sync issues here

sent 10k to f1f1594aafa9ebda5e1e0aa09af8d0d3ff324ea793c0d1d87bcd28d2  

also i decreased the network spamming, bacause that was way too much, fee expenses were 0.06/30s, that is 0.002 bismuth per second, 0.12 bismuth per minute, 7.2 bismuth per hour
might be a little too little

[bones261]

I can see two mining attempts which were rejected due to chain reorganization



or perhaps these are normal transactions

so far no sync issues here

sent 10k to f1f1594aafa9ebda5e1e0aa09af8d0d3ff324ea793c0d1d87bcd28d2 

also i decreased the network spamming, bacause that was way too much, fee expenses were 0.06/30s, that is 0.002 bismuth per second, 0.12 bismuth per minute, 7.2 bismuth per hour
might be a little too little

That would have been me doing the mining attempts. Am I doing something wrong? I also think that I was the one that sent the missing transaction and mined the block in the previous post you made about network problems.

[Bangc]

give me a little bismuth

199a04ab4169547affa627f6b5e689a80e358a2da5dda4eb14aed64a

I want to try

[HCLivess]

I can see two mining attempts which were rejected due to chain reorganization



or perhaps these are normal transactions

so far no sync issues here

sent 10k to f1f1594aafa9ebda5e1e0aa09af8d0d3ff324ea793c0d1d87bcd28d2  

also i decreased the network spamming, bacause that was way too much, fee expenses were 0.06/30s, that is 0.002 bismuth per second, 0.12 bismuth per minute, 7.2 bismuth per hour
might be a little too little

That would have been me doing the mining attempts. Am I doing something wrong? I also think that I was the one that sent the missing transaction and mined the block in the previous post you made about network problems.

Nothing wrong I assume, but we might be making too many blocks in too little time (this is expected with instant transactions). There was only one node fully synced to me (at one time), it disconnected, and then I arbitrarily deleted half of my blockchain to test if syncing works properly now (then sent some new txs to it), so your transactions got resubmitted from shorter to longer chain, but in a different order now. I will let Bismuth do it's thing now without abruptions for some time to see if the sync finally works or not

In short, there was a day-long fork due to testing

[HCLivess]

give me a little bismuth

199a04ab4169547affa627f6b5e689a80e358a2da5dda4eb14aed64a

I want to try

Please make sure you have your address submitted to https://docs.google.com/forms/d/1-zNSIyQ3lKoN5IlraQKZ7tEfhk6HduSVwuyLev0gOLk
I will be sending to those addresses regularly. Mind you this is testnet, so if you create a new account just to receive coins, you will not achieve any self-enrichment

[HCLivess]

Here are the latest mining rewards, the blockchain still holds stable and solid



I see someone modified the miner not to send any bismuth when mining, well done 
although the fee is calculated independently

[Bangc]

After receiving the wrong "blockfound_"
(block_height == 0)

"ledger.db" is broken

[HCLivess]

After receiving the wrong "blockfound_"
(block_height == 0)

"ledger.db" is broken

Thanks, never seen this issue before, what version are you running?
Do you have a log entry for that, please? And a copy of your blockchain if possible
I would love to know if you received it from my node, but it must be since there are no other nodes
I am still patiently waiting for someone to do the rollback hack before I fix it

[Bangc]

After receiving the wrong "blockfound_"
(block_height == 0)

"ledger.db" is broken

Thanks, never seen this issue before, what version are you running?
Do you have a log entry for that, please? And a copy of your blockchain if possible
I would love to know if you received it from my node, but it must be since there are no other nodes
I am still patiently waiting for someone to do the rollback hack before I fix it

from My TestCode

import hashlib
import sqlite3
import socket
import time
import base64
from Crypto.PublicKey import RSA
from Crypto.Signature import PKCS1_v1_5
from Crypto.Hash import SHA

# import keys
key = RSA.importKey(open('privkey.der').read())
public_key = key.publickey()
private_key_readable = str(key.exportKey())
public_key_readable = str(key.publickey().exportKey())
address = hashlib.sha224(public_key_readable).hexdigest()

s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
#s.settimeout(1)
s.connect(("0.0.0.0", int("2829")))
print "Connected"

#enter transaction start
conn = sqlite3.connect('ledger.db')
c = conn.cursor()

apiKey = 'blockfound_'
makeTimeStamp = 2.00
makeFromAddress = 'genesis'
makeToAddress = '07fb3a0e702f0eec167f1fd7ad094dcb8bdd398c91999d59e4dcb475'
makeAmount = 1.1
makefee = 1.0
reward = 0

transaction = str(makeTimeStamp) + ":" + str(makeFromAddress) +":" + str(makeToAddress) +":"+ str(makeAmount)

h = SHA.new(transaction)
signer = PKCS1_v1_5.new(key)
signature = signer.sign(h)
signature_enc = base64.b64encode(signature)
print "Client: Encoded Signature: "+str(signature_enc)


txhash_new = hashlib.sha224(str(transaction) + str(signature_enc) + str('BangC')).hexdigest()

c.execute("INSERT INTO transactions VALUES ('" + str(0) + "','" + str(
   makeTimeStamp) + "','" + str(makeFromAddress) + "','" + str(makeToAddress) + "','" + str(
   float(makeAmount)) + "','" + str(signature_enc) + "','" + str(
   public_key_readable) + "','" + str(txhash_new) + "','" + str(makefee) + "','" + str(
   reward) + "')")
c.execute("SELECT * FROM transactions WHERE block_height='" + str(
   0) + "'")
txhash_send = c.fetchone()
c.execute("delete FROM transactions WHERE block_height ='"  + str(0) + "'")

conn.commit()
conn.close()

s.sendall(apiKey)
time.sleep(0.1)
txhash_len = len(str(txhash_send))
while len(str(txhash_len)) != 10:
   txhash_len = "0" + str(txhash_len)
s.sendall(str(txhash_len))
time.sleep(0.1)
s.sendall(str(txhash_send))

[ecawyna]

nice logo. very alienish. 

[HCLivess]

After receiving the wrong "blockfound_"
(block_height == 0)

"ledger.db" is broken

Thanks, never seen this issue before, what version are you running?
Do you have a log entry for that, please? And a copy of your blockchain if possible
I would love to know if you received it from my node, but it must be since there are no other nodes
I am still patiently waiting for someone to do the rollback hack before I fix it

from My TestCode

import hashlib
import sqlite3
import socket
import time
import base64
from Crypto.PublicKey import RSA
from Crypto.Signature import PKCS1_v1_5
from Crypto.Hash import SHA

# import keys
key = RSA.importKey(open('privkey.der').read())
public_key = key.publickey()
private_key_readable = str(key.exportKey())
public_key_readable = str(key.publickey().exportKey())
address = hashlib.sha224(public_key_readable).hexdigest()

s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
#s.settimeout(1)
s.connect(("0.0.0.0", int("2829")))
print "Connected"

#enter transaction start
conn = sqlite3.connect('ledger.db')
c = conn.cursor()

apiKey = 'blockfound_'
makeTimeStamp = 2.00
makeFromAddress = 'genesis'
makeToAddress = '07fb3a0e702f0eec167f1fd7ad094dcb8bdd398c91999d59e4dcb475'
makeAmount = 1.1
makefee = 1.0
reward = 0

transaction = str(makeTimeStamp) + ":" + str(makeFromAddress) +":" + str(makeToAddress) +":"+ str(makeAmount)

h = SHA.new(transaction)
signer = PKCS1_v1_5.new(key)
signature = signer.sign(h)
signature_enc = base64.b64encode(signature)
print "Client: Encoded Signature: "+str(signature_enc)


txhash_new = hashlib.sha224(str(transaction) + str(signature_enc) + str('BangC')).hexdigest()

c.execute("INSERT INTO transactions VALUES ('" + str(0) + "','" + str(
   makeTimeStamp) + "','" + str(makeFromAddress) + "','" + str(makeToAddress) + "','" + str(
   float(makeAmount)) + "','" + str(signature_enc) + "','" + str(
   public_key_readable) + "','" + str(txhash_new) + "','" + str(makefee) + "','" + str(
   reward) + "')")
c.execute("SELECT * FROM transactions WHERE block_height='" + str(
   0) + "'")
txhash_send = c.fetchone()
c.execute("delete FROM transactions WHERE block_height ='"  + str(0) + "'")

conn.commit()
conn.close()

s.sendall(apiKey)
time.sleep(0.1)
txhash_len = len(str(txhash_send))
while len(str(txhash_len)) != 10:
   txhash_len = "0" + str(txhash_len)
s.sendall(str(txhash_len))
time.sleep(0.1)
s.sendall(str(txhash_send))

Did not know you were using a custom code implementation, interesting.
I would love to know whether this code breaks only your node or if it breaks other nodes if you use it to communicate with them. Unfortunately, there is nothing we can do on the client-side to prevent ledger from breaking, that all goes to what operations you decide to perform on the database. However, there could be some recovery features later on - for now the only fix is to resync the ledger from the installation (and back it up if you do experiments)

[HCLivess]

nice logo. very alienish. 

Thanks, that is a medieval chemical logo with Bismuth as the actual background overlay

[HCLivess]

Could we get a cooperated mining + spamming operation? 
In an attempt to break the network

[HCLivess]

blockchain broken again   one tx missing, ill check what went wrong
EDIT: unified mempool lock handling (pushed, unreleased)

EDIT: I would like to thank the two active (open port) nodes for participating in the testnet, very much appreciated

[Bangc]

Not synchronized since 6225

[HCLivess]

Not synchronized since 6225

Thanks, my node might be actually down at the moment. I will check from home -> OK, so somehow I send 6226, but it is not added to your blockchain. Might be a db issue (similar to what used to happen to me). You can either send me the blockchain or see for yourself if the numbers align using "DB Browser for SQLite". Also please make sure your ledger.db is not locked for writing.

Found the issue: The transaction you did not receive has an invalid signature according to client.
I will check, not sure how it would spread though... Must be some float conversion mess

Also, I have decided there will be NO ICO for Bismuth, based on feedback. However, I may release a fork of Bismuth in the future, which will be ICO for an enterprise version of Bismuth (older stable version), a model similar to that of Fedora and RedHat

[HCLivess]

Looks like signature verification was weak in several places, will release a hotfix soon

[duts_bg]

Is there a user friendly documentation on how to mine on testnet in windows?