Main Menu

Test Net for Advanced Users

Started by bytemaster, August 14, 2015, 10:39:33 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

spartako

wallet_account_set_approval spartako

abit

Quote from: Xeldal on September 19, 2015, 02:26:53 PM
In the meantime can someone send me (xeldal) 11 - 20 CORE so I can "set_voting_proxy"

Thanks
Transferred.
BitShares committee member: abit
BitShares witness: in.abit

abit

BitShares committee member: abit
BitShares witness: in.abit

Xeldal

Cant create a backup for whatever reason.
https://bitsharestalk.org/index.php/topic,18511.0.html

In the meantime can someone send me (xeldal) 11 - 20 CORE so I can "set_voting_proxy"

Thanks


abit

Quote from: bytemaster on September 19, 2015, 02:07:08 PM
Please do not vote out init0 -> init11 these are our nodes for testing in this test network and they are on separate machines / processes and not all on one machine.

Please DO vote for init0->init11  AND everyone on this thread so we can increase the total number of witnesses.
How to increase the total number of witnesses? Do we need a proposal?
BitShares committee member: abit
BitShares witness: in.abit

CalabiYau

Voted:
bitcube
calabiyau
dele-puppy
delegate-1.lafona
delegate-clayop
fox
in.abit
init0
init1
init2
init3
init4
init5
init6
init7
init8
init9
init10
init11
riverhead
wackou
xeldal
spartako


spartako

Quote from: puppies on September 19, 2015, 01:59:13 PM


We need to vote for more witnesses than the 11 that are currently in.  The number of active witnesses is determined by the average number that we are all voting for.  I am assuming this is based upon stake voting. 

I am voting in gui, so I cant help with the cli syntax, but you can always set me as a proxy.  I am currently voting for

I just set you as a proxy:

set_voting_proxy spartako dele-puppy true


Please add "spartako" (1.6.4232) to the list, thanks!
wallet_account_set_approval spartako

bytemaster

Votes are only calculated once per hour, so they will not show up until the next maintenance interval.
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
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.

bytemaster

Please do not vote out init0 -> init11 these are our nodes for testing in this test network and they are on separate machines / processes and not all on one machine.

Please DO vote for init0->init11  AND everyone on this thread so we can increase the total number of witnesses.
For the latest updates checkout my blog: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
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.

CalabiYau

Thx spartako, funds arrived - votes not showing up till now.   


spartako

Quote from: abit on September 19, 2015, 01:58:30 PM
Quote from: spartako on September 19, 2015, 01:42:18 PM
I am really confused  ???
There is a bug with voting in cli-wallet. It's only possible to vote for one witness via "vote_for_witness" -- the last one.
You can try vote-proxy or try GUI if you want to vote for more witnesses.

The "total_votes: 0" is also buggy. It will show non-zero only if your witness have ever been voted in.

Thanks! Now it is more clear
wallet_account_set_approval spartako

puppies

please whitelist me for ABITUSDA.

In regards to voting, it seems as if votes are not showing up in get_witness until you are voted in.  Even if you are voted in, they only update once an hour. 

We need to vote for more witnesses than the 11 that are currently in.  The number of active witnesses is determined by the average number that we are all voting for.  I am assuming this is based upon stake voting. 

I am voting in gui, so I cant help with the cli syntax, but you can always set me as a proxy.  I am currently voting for
bitcube
calabiyau
dele-puppy
delegate-1.lafona
delegate-clayop
fox
in.abit
init1
init2
init3
init4
init5
init6
init7
init8
init9
riverhead
wackou
xeldal
[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

abit

Quote from: spartako on September 19, 2015, 01:42:18 PM
I am really confused  ???
There is a bug with voting in cli-wallet. It's only possible to vote for one witness via "vote_for_witness" -- the last one.
You can try vote-proxy or try GUI if you want to vote for more witnesses.

The "total_votes: 0" is also buggy. It will show non-zero only if your witness have ever been voted in.
BitShares committee member: abit
BitShares witness: in.abit

spartako

Quote from: Xeldal on September 19, 2015, 01:08:43 PM
I still have 0 votes.

I've changed my witness name to just xeldal   ,thinking that may be why.

Please update your votes for this witness.  Thankyou

get_witness xeldal
{
  "id": "1.6.4949",
  "witness_account": "1.2.86459",


Me too I have 0 votes and it is really strange, I try to understand how voting is working:

If I type:

vote_for_witness spartako init0 true true

I obtain:

....
"new_options": {
          "memo_key": "GPH5mgup8evDqMnT86L7scVebRYDC2fwAWmygPEUL43LjstQegYCC",
          "voting_account": "1.2.5",
          "num_witness": 0,
          "num_committee": 0,
          "votes": [
            "1:0",
            "1:623"
          ],
          "extensions": []
....


So if I understood well I voted for 1:0 and 1:623, the vote id correspond to init0 and bitcube:

get_witness init0
{
  "id": "1.6.1",
  "witness_account": "1.2.100",
  "last_aslot": 22268,
  "signing_key": "GPH6gBqcGKgkVQvt7XZtYN9z3QHdWFCGKB2oiNvpMkXQsMqZB1YWi",
  "pay_vb": "1.13.12",
  "vote_id": "1:0",
  "total_votes": "2074182939478",
  "url": "bitshares.org",
  "total_missed": 71
}



get_witness bitcube
{
  "id": "1.6.624",
  "witness_account": "1.2.8206",
  "last_aslot": 0,
  "signing_key": "GPH7qbi1TEAFGjsCTNQoecnGkcMr3RV6ya5yc8GbXyXCV1adQtFsn",
  "vote_id": "1:623",
  "total_votes": 0,
  "url": "",
  "total_missed": 0
}


If then I give the command:

vote_for_witness spartako init1 true true


I obtain:

....
"new_options": {
          "memo_key": "GPH5mgup8evDqMnT86L7scVebRYDC2fwAWmygPEUL43LjstQegYCC",
          "voting_account": "1.2.5",
          "num_witness": 0,
          "num_committee": 0,
          "votes": [
            "1:1",
            "1:623"
          ],
....


It seems that I continue to vote for bitcube but no more for init0, instead I vote for init1

And so on if I vote for init2 I obtain:

...
"new_options": {
          "memo_key": "GPH5mgup8evDqMnT86L7scVebRYDC2fwAWmygPEUL43LjstQegYCC",
          "voting_account": "1.2.5",
          "num_witness": 0,
          "num_committee": 0,
          "votes": [
            "1:2",
            "1:623"
          ],
          "extensions": []
        },
....


I am really confused  ???
wallet_account_set_approval spartako

abit

#957
Since it's unable to short bitUSD right now, welcome to trade on my private bitAsset "ABITUSDA".
Short is enabled here. Current settlement price is 1 BITUSDA = 1 CORE.
Anyone who wants to publish price feeds for the asset please leave a message here, so that I can add him/her to the authorized list.
The command for publishing price feed is like:

publish_asset_feed in.abit ABITUSDA {"settlement_price":{"base":{"amount":50000,"asset_id":"1.3.662"},"quote":{"amount":1000000000,"asset_id":"1.3.0"}},"core_exchange_rate":{"base":{"amount":100000,"asset_id":"1.3.0"},"quote":{"amount":10000,"asset_id":"1.3.662"}}} true


In which,
* in.abit is my account name, so replace with your name
* ABITUSDA is the name of asset
* "1.3.662" is ID of the asset, "1.3.0" is CORE
Fill the other numbers as you like.
BitShares committee member: abit
BitShares witness: in.abit