Hi, I have a private testnet where I'd like to change the fee schedule. I've tried with the following:

# Create proposal
propose_fee_change init0 "2020-06-01T00:00:00" {"transfer":{"fee":1000000,"price_per_kbyte":10000}} true

# Approve proposal
approve_proposal init0 1.10.1 {"active_approvals_to_add" : ["init0"]} true
But it doesn't seem to work. What am I doing wrong?

Dear BitShares community,

I've noticed that some users are attempting to try their luck with "asset flipping" (similar to domain flipping) - or at least it seems like it. Take for example: https://wallet.bitshares.org/#/account/blokzinciri.org who registered multiple "core assets" such as https://wallet.bitshares.org/#/asset/WEALTH but never use it for anything.

In my opinion this can become a problem for BitShares because someone could simply acquire a lot of "core assets" and wait for someone to buy it for a high premium. This could potentially scare organizations away from creating new gateways if they cannot get the "core assets" they are looking for.

Obviously, its first-come-first-serve just like when you buy a traditional web domain such as .net .com etc. but I think BitShares could benefit from preventing excessive "core asset" registration by for example:
1) increase the costs of creating new "core assets"
2) add a yearly fee to hold a "core asset"
3) require a certain volume of transactions between the "core asset" and (BTS, bitUSD...)

These are just examples. Please let me know what you think...? Also I would like to know how I can make this an official proposal to the BitShares Community - who should I contact?

http://docs.bitshares.org/testnet/index.html is pointing to http://testnet.bitshares.eu/ but its not working? Is there no longer a public testnet available?

Quick update on the progress. I now have two witness nodes connecting to the same ES.

• witness_node #1 was in sync and connected to ES
• witness_node #2 was then started from scratch (Block 0), being connected to the same ES

No additional errors was seen on witness_nodes or ES after attaching witness_node #2.

The only error seen is this:
fullnode         | 2582979ms th_a       database_api.cpp:282          ~database_api_impl   ] freeing database api 2748370832
fullnode         | 2583114ms th_a       application.cpp:512           handle_block         ] Got block: #26867021 time: 2018-05-10T21:43:03 latency: 114 ms from: fox  irreversible: 26867003 (-18)
fullnode         | 2583119ms th_a       elasticsearch.cpp:66          SendBulk             ] error: Unknown error
fullnode         | 2583119ms th_a       es_objects.cpp:99             updateDatabase       ] Error sending data to database
fullnode         | 2583165ms th_a       database_api.cpp:263          database_api_impl    ] creating database api 2336441072
fullnode         | 2583166ms th_a       database_api.cpp:263          database_api_impl    ] creating database api 2622826080The error was however already present before connecting witness_node #2 to ES. I guess this is normal behaviour?

Turns out, it was a stupid mistake (hard to spot) because there error messages is either not there or they do not repeat in the console output. The problem was double quoutes here:

      - BITSHARESD_ES_NODE_URL="http://elasticsearch:9200/"

Here is a working docker-compose.yml
version: '3'
services:
  elasticsearch:
    image: docker.elastic.co/elasticsearch/elasticsearch:6.2.4
    container_name: elasticsearch
    environment:
      - ELASTIC_PASSWORD=secret
      - cluster.name=docker-cluster
      - discovery.type=single-node
      - bootstrap.memory_lock=true
      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
    networks:
      stack:
    ulimits:
      memlock:
        soft: -1
        hard: -1
    volumes:
      - esdata:/usr/share/elasticsearch/data
    ports:
      - 9200:9200

  fullnode:
    image: bitshares/bitshares-core:latest
    container_name: fullnode
    environment:
      - BITSHARESD_PLUGINS=witness elasticsearch market_history
      - BITSHARESD_ES_NODE_URL=http://elasticsearch:9200/
      - BITSHARESD_RPC_ENDPOINT=0.0.0.0:8090
      - BITSHARESD_P2P_ENDPOINT=0.0.0.0:9090
      - BITSHARESD_WITNESS_ID="1.6.122"
      - BITSHARESD_PRIVATE_KEY=["BTS...","5..."]
    networks:
      stack:
    ports:
      - 9090:9090
      - 8090:8090
    volumes:
      - fullnode:/var/lib/bitshares
    depends_on:
      - elasticsearch

volumes:
  fullnode:
  esdata:

networks:
  stack:

Next question:
Is it possible to run multiple witness_nodes, that's sharing the same ElasticSearch or will it cause conflicts such as double inserts / race conditions or anything else like that? Basically, I'd like to host multiple witness_nodes across the globe to ensure high availability and low latency.

I'd like to suggest a few feature/improvements for the witness_node.

1) Add support for multiple CPU cores. The witness_node is only using 1 CPU core at the moment, which means that certain tasks like --replay-blockchain takes forever.

2) When a witness_node is starting up, it should print a preview of the configuration parameter/values it is using. This preview would be very useful while debugging/configuring the node for the first time. Currently the witness_node can be configured using command-line arguments and config.ini. If both are used, a CLI argument might override the config.ini parameter.

Hi, move BTC or another currency to your account, from another exchange such as coinbase/bitstamp etc. and then convert e.g. BTC to BTS ?

Assume you have multiple full nodes / witness nodes (e.g. 10 seperate servers, spread across the world). Can those 10 witness_node processes share the same --data-dir ("witness_node_data_dir") or will it cause some sort of file lock / race condition issue?

The reason for asking is that every time you setup a new witness node is takes many hours before the blockchain have been retrived and stored in the witness_node_data_dir.

If they different processes cannot work on the data data-dir is it then possible to copy/paste a fully loaded data-dir to another "empty" witness node?