Topic: [TESTNET]Bismuth - New Language, Interpretation Engines, DAPPs - page 22. (Read 49748 times)

hello can people still participate in the testnet ?

i did not mange to try the testnet ... what would be the distribution model for first phase i wish it could be the 1 core cpu and limited mining per IP like early day on vanilla coin aka Vcash now the distribution was really fair at first and everyone hold their vanilla really dear .. would we see something similiar on bismuth at first ?  

jap, tested on 0.9. And when i launch node then there shows some invalid transactions and only then starting download blocks.

sry if im repeating and you know already problem, then just ignore me I as a tester report about everything that looks strange ))

Hey HCLivess,
I hope to find some time to test Bismuth, it's looking more interesting every update that is made.
I was hoping to run the test client on a gui less Linux server. Could I perhaps run a node on a server and use a gui wallet on OSX to connect to said server node? Or would it be more feasible to simply run the client in a non-gui mode and try to use command line for testing, sending, receiving etc? Is the gui needed for some functionality or simply being much more user friendly?

Next version will have a proper rollback mechanism, current one is quite wild. However, there will still be some rollbacks, I will work on optimizations though. Are you testing version 0.9? Upgrades in 0.9 have major impact on transaction collisions appearing in previous versions.

still problem with block height? because sometimes when manualy refresh blocks, numbers going up and down, maybe its just gui bag, no idea))

I created a new poll


https://github.com/hclivess/Bismuth/issues/20

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

Hi, I haven't thought about that yet. How much does the mining algorithm take for you?
It seems to take 1 core of my laptop, once a GPU miner is developed (I have no idea how to do that), GPU should be just as demanding as CPU currently (limited by the actual hashrate).

Hi, more like a design flaw, thanks for pointing out. To be honest, this is my first network application. I am using a python TCP server module for active nodes and simple sockets for clients.


I thought this piece of code was handling it, but it is not so reliable (also conenctions get stuck in consensus pool)

 I will look into this after finishing work on putting block operations into functions and switching the transaction engine from restrictive to omissive - done today. It will bring some overhead, but performance and reliability will be boosted.

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

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

Need to rework the tx engine

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

Interesting, will be following this.

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

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

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

Watching, looks like an interesting project.