Author Topic: BTSX 0.4.5 Bug Fix Status Update  (Read 4846 times)

0 Members and 1 Guest are viewing this topic.

Offline Riverhead


Offline dxtr

  • Full Member
  • ***
  • Posts: 71
  • United We Stand, Dispersed We Are.
    • View Profile
« Last Edit: August 22, 2014, 03:50:18 pm by dxtr »
Help me out:     wallet_approve_delegate mr.scroodge true

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
It's AWESOME how quickly you can resolve those bugs!! +5%

they are typing almost quicker than thinking...

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
It's AWESOME how quickly you can resolve those bugs!! +5%

Offline bytemaster

We think we have found a fix for the transaction ledger errors reported here:

https://github.com/BitShares/bitshares_toolkit/issues/657

We are testing that now. 
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline bytemaster

We have identified the cause of syncing issues... a race condition on which nodes can serve you the chain first.  If you happen to connect to an un-upgraded node and fetch their chain first then you will be unable to finish syncing.   The chain server should fix this in the current version and the next version is putting in extra code to handle this case.

https://github.com/BitShares/bitshares_toolkit/wiki/Using-Chain-Servers
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline bytemaster

We are preparing a post about using a Chain Server for rapid download from a trusted source.  Nathan is preparing a How To.  For those having trouble syncing directly from P2P clients this alternative may work for you.


Good news. Are we talking Electrum like functionality or a pre-indexed blockchain?

Single source fire-hose of all blocks... rather than the much more complex algorithm required for P2P syncing.  Performance is significantly better for "catching up".

We do have Electrum-like functionality on the roadmap and partly designed. 
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline Riverhead

We are preparing a post about using a Chain Server for rapid download from a trusted source.  Nathan is preparing a How To.  For those having trouble syncing directly from P2P clients this alternative may work for you.


Good news. Are we talking Electrum like functionality or a pre-indexed blockchain?

Offline bytemaster

We have a mitigating fix for the network crash pending in the toolkit repository.  We will have to wait for DAC Sun Limited to update their master branch.

Some general observations for delegates:
1) Your client is more likely to crash if you have more connections.
2) We are preparing a new command line argument that will disable incoming connections
3) We recommend delegates produce blocks from a node with no incoming connections and perhaps 20 outgoing connections.
4) We recommend delegates ALSO host a public node with a lot of connections to support the network.
5) If the computer has enough RAM running both on the same machine is possible.

We are preparing a post about using a Chain Server for rapid download from a trusted source.  Nathan is preparing a How To.  For those having trouble syncing directly from P2P clients this alternative may work for you. 
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani

Offline Riverhead

Wait, you created a bug against the tool kit and I created it against DACSunLimited. I guess it is the tool kit and their build is on top of that. I'll delete my bug and we'll use yours.

I've never logged a bug before, just created my Git Hub account today. Such a noob :P .
« Last Edit: August 22, 2014, 01:43:58 pm by Riverhead »



Offline Riverhead

« Last Edit: August 22, 2014, 01:29:32 pm by Riverhead »

Offline bytemaster

Where do you want us to send/post the P2P logs?

Post links to the github issues.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.