[Public Testnet] testnet.bitshares.eu

[noisy]

I think I added witness called "issuer", but it is not appear on http://testnet.bitshares.eu/#/explorer/witnesses, but I still have Votes: 0.

Should I do something more or a committee member has to vote for this witness?

[abit]

Ask xeroc for funds. Ask xeroc for electing your witnesses so that you can publish price feeds.

Those two can be done even without xeroc's help - each new account in the web GUI is well funded by default.

Not enough.
Xeroc votes with 9.8 billion for his own witnesses (from the faucet account). Every new account get funded with 1 million only. Unless you create 10K accounts and all vote for your witness. You can try create 5K accounts (with a script maybe) so your combined voting power will be higher than faucet.
Or maybe you only need to vote for all current active witnesses + your witness, so the total number of active witnesses will increase by 1, so you're voted in?

//Update: init9 is voted in with 0 votes, so there is at least one witness position available in testnet. However I think it's best if at least 3 witnesses provide price feeds to a MPA.

[xeroc]

@xeroc
I think you haven't copied some js widgets for the testnet web GUI.
As a result, some features are malfunctioning e.g. the settings pop-up for the price history chart does not work.

Compare:
https://bitshares.openledger.info/widgets/1/w.js
with the missing file here:
http://testnet.bitshares.eu/widgets/1/w.js

Interesting. I though those would be installed automatically by `npm` .. @svk: do you know more?

[jakub]

Ask xeroc for funds. Ask xeroc for electing your witnesses so that you can publish price feeds.

Those two can be done even without xeroc's help - each new account in the web GUI is well funded by default.

[abit]

My thinking is that we need to make as clear as possible that this is a testnet and it's tokens are worthless.

I agree. But I would like to treat a testnet like a staging environment, where things should be as close as possible to real network. Maybe an alert/reminder after loading a page would be enough?

Calling them USD and pegging them similar to BTS:USD is counterproductive imho ..

In my opinion we have too many assets, what is very confusing for new users. For example, we have BTC, openBTC, metaBTC, etc. now we are going to have even more assets in the testnet, like PEG.FAKEBTC, because without making a pegged assets there is no possibility of creating those assets by collateral. Am I right?

You can create those assets by yourself if they're currently not available. Ask xeroc for funds. Ask xeroc for electing your witnesses so that you can publish price feeds.

[jakub]

@xeroc
I think you haven't copied some js widgets for the testnet web GUI.
As a result, some features are malfunctioning e.g. the settings pop-up for the price history chart does not work.

Compare:
https://bitshares.openledger.info/widgets/1/w.js
with the missing file here:
http://testnet.bitshares.eu/widgets/1/w.js

[xeroc]

Yes, i noticed that too and there is a bug report about whatever went wrong with the embedded genesis block.

I'll let vote you in asap

[jakub]

I've managed to add a witness node to the testnet.
It's called neura-sx and it runs on a Ubuntu server.

There were no issues while setting up the witness, expect for this one: the embedded version of the genesis.json file did not work for me as it generated a wrong blockchain ID.

The workaround is simple: apply the genesis.json file manually like this:

Code Select Expand


graphene-testnet/programs/witness_node/witness_node --genesis-json graphene-testnet/genesis.json --witness-id '"<your-witness-id>"' --private-key '["<your-witness-public-key>","<your-witness-private-key>"]'


[noisy]

My thinking is that we need to make as clear as possible that this is a testnet and it's tokens are worthless.

I agree. But I would like to treat a testnet like a staging environment, where things should be as close as possible to real network. Maybe an alert/reminder after loading a page would be enough?

Calling them USD and pegging them similar to BTS:USD is counterproductive imho ..

In my opinion we have too many assets, what is very confusing for new users. For example, we have BTC, openBTC, metaBTC, etc. now we are going to have even more assets in the testnet, like PEG.FAKEBTC, because without making a pegged assets there is no possibility of creating those assets by collateral. Am I right?

[xeroc]

There is a PEG.FAKEUSD for that purpose and it should have a price feed.

I will not use USD to make clear the those tokens are worthless

Testnet in my opinion should looks like ideal place to trade assets. USD:BTC exchange should behave like a real exchange. All assets like USD, BTC, EUR, GOLD, SILVER should have price feeds. Ours bots should provide a liquidity for those markets :)

In my opinion we should just add the reminder about fact, that this is just a test network to footer of wallet. We already emphasize that with URL address. Additional information (more elaborated) could be in deposit-withdraw section.

I completely removed the deposit-withdraw section from the account settings, so that shouldn't be a big deal.
My thinking is that we need to make as clear as possible that this is a testnet and it's tokens are worthless. Calling them USD and pegging them similar to BTS:USD is counterproductive imho ..
But I certainly agree that everyone should put a bot into PEG.FAKEUSD:TEST

[noisy]

There is a PEG.FAKEUSD for that purpose and it should have a price feed.

I will not use USD to make clear the those tokens are worthless

Testnet in my opinion should looks like ideal place to trade assets. USD:BTC exchange should behave like a real exchange. All assets like USD, BTC, EUR, GOLD, SILVER should have price feeds. Ours bots should provide a liquidity for those markets :)

In my opinion we should just add the reminder about fact, that this is just a test network to footer of wallet. We already emphasize that with URL address. Additional information (more elaborated) could be in deposit-withdraw section.

[merivercap]

@xeroc please correct me if am wrong, but I think right now there is no possibility to create USD in testnet, because borrowing is possible only for assets which has price feed.

Could you run a price feed for all bitAssets which has price feed in real network? Could you add a documentation how to run such price feed for all assets for testnetwork?

@noisy BTW feel free to play around with PEG.FAKEUSD if you are ok with some parameter tweaks... it uses one price-feed from Poloniex.   
(Note:  Parameters are: MSSR: 100.1%, MCR: 175%, forced settlement at 90%)

[xeroc]

There is a PEG.FAKEUSD for that purpose and it should have a price feed.

I will not use USD to make clear the those tokens are worthless

[noisy]

@xeroc please correct me if am wrong, but I think right now there is no possibility to create USD in testnet, because borrowing is possible only for assets which has price feed.

Could you run a price feed for all bitAssets which has price feed in real network? Could you add a documentation how to run such price feed for all assets for testnetwork? 

[jakub]

This is the genesis.json file that you receive when you clone the repo:
The above file produces the "wrong" blockchain id.

Whereas this is the genesis.json file that you receive when you download a zipped version of the repo:
The above file produces the "correct" blockchain id.

Differences are the line feeds aka "\r" or 0D in hex.
The first one is in windows text file format, which has both "\r"s and "\n"s, or 0D 0A in hex.
The second one is in linux text file format, which has only "\n"s, or 0A in hex.

So the difference may come from:
* editor settings
* git repo settings
* git client settings
* zip tool settings

Thoughts?

The thing is, those slight differences produce different behavior of the witness node.
The process of calculating the blockchain id seems to depend on those small differences.
And xeroc seems to have similar issues on Linux.

IMO, it's a bug.