puppies I have just "flood" you some 1 CORE transactions.

On my second round I sent 8,421.  at 1  core interval. This was done brute forced Hyper Olympics style https://www.youtube.com/watch?v=8va4YGGA3wE, so I am not convinced I did submit as many in 1 minute.

Anyway my witness has not died, can you check you got something?

Anybody having problems with transactions?

It has taking me lots of attempts to import my balances, and I cannot vote myself. I had but the votes remain 0.

you can vote me in to test @ betaxtrade

Yes I was thinking about doing exactly the same... but remember the issues that had poloniex  a while ago.

I found some problems related to spam transactions.

1) In a normal node without block production, when spam transactions occurred (in my case 100 txs in few seconds), block sync stops for about 3 minutes.

2) In a witness node with block production, spam transactions caused witness node crash. In this case, I have to resync my witness node.

3) Only part of spam transactions are accepted. I sent a hundred transactions but only 9 out of 100 are shown.

Im rebuilding, was travelling yesterday,  once done I will do the same and confirm on my side.

Assume a worker proposal is submitted for some kind of 'app' for BitShares.

Could the worker of the app be able to built into it a fee per transaction or something like that in order to profit from it and/or continue maintenance and development?

In other words is there room for contributor proposals of bitshares to allow them to profit on a per/app basis?

If not, would they be able to build into it perhaps something like a UIA of their own which the feature runs through and charges a fee perhaps.. or does everything have to be 'assimilated' into BTS?

Thanks for the clarification!

+ If for example somebody wants to create extensions (imagine Augur) how will these be licensed.
+ What is the process for this.

For those eagerly waiting .. here is another howto
https://github.com/cryptonomex/graphene/wiki/Howto-import-an-existing-delegate-as-witness-in-BitShares-2.0

Nice! I have just done a small correction on --witness-id '"<witnessid>"'

I was able to delete my files and resync the witness, then I turned block production back on and it seems to be working now.

Here are some examples of how to use docker to run the witness:

Start a witness, all logs and data will be dumped right after execution stops:
docker run -it --rm sile16/graphene-witness:aug19test --genesis-json /aug-19-puppies-test-genesis.json -s 45.55.6.216:1776
(this docker image i included the genesis json in)

Start a witness with persistent data dir:
docker run -it --rm -v <local data dir>:/witness_node_data_dir sile16/graphene-witness:aug19test --genesis-json /aug-19-puppies-test-genesis.json -s 45.55.6.216:1776

to make it easier to expose ports you can also include --net=host
docker run -it --rm --net=host -v /witness_node/test_net2:/witness_node_data_dir sile16/graphene-witness:aug19test --genesis-json /aug-19-puppies-test-genesis.json -s 45.55.6.216:1776 --rpc-endpoint 127.0.0.1:8090


the docker image is pushed so these commands should work for anyone.

 

Hi im in for this month