Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - abit

Pages: 1 2 3 4 5 6 [7] 8 9 10 11 12 13 14
92
The committee is voting on a fee adjustment proposal: https://cryptofresh.com/p/1.10.2657

All fees are proposed to be reduced by around 83%, or say around 6x -> 1x.

It's based on the idea of USD-Denominated fee schedule which was discussed in this thread: https://bitsharestalk.org/index.php?topic=21368.0

93
Exchange: https://19800.com/market/cny_bts/

API: http://www.bixun.info/forum.php?mod=viewthread&tid=543

Code: [Select]
$ curl "https://19800.com/api/v1/ticker?market=cny_bts&nonce=12301231312312321312"
{"data":{"High":0.8,"Low":0.6,"LastPrice":0.75,"TopBid":0.75,"TopAsk":0.753,"Volume":10042142.01421782,"Increase":0.07604},"code":1,"msg":""}

Recent volume is similar to Bittrex.

95
General Discussion / Committee Proposal: Network Fee Adjustment
« on: May 01, 2017, 06:44:07 am »
The committee is voting on a fee adjustment proposal: https://cryptofresh.com/p/1.10.1899

All fees are proposed to be reduced by around 50%.

//Edit:
It's based on the idea of USD-Denominated fee schedule which was discussed in this thread: https://bitsharestalk.org/index.php?topic=21368.0

96
General Discussion / Remove OKCoin and etc from price feed source?
« on: February 10, 2017, 10:54:49 am »
They suspended BTC withdrawal, so no longer free markets, so prices on their markets can't be trusted. Thoughts?

97
General Discussion / About worker price
« on: January 12, 2017, 09:05:39 am »
This is an interesting article (written by BM): Building Long Term Value from your

98
中文(Chinese) / 【教程】使用资产白名单功能
« on: September 09, 2016, 04:06:33 pm »
【概述】

资产设好了白名单后,不在名单内的账号,将不能对该资产进行转账(包括转入转出)、交易(包括买入卖出),不能使用该资产支付系统手续费。至于已经启动的分期付款是否可以继续执行,或者发行人可否强制收回该账户拥有的资产,或者其他高级功能,有待测试。

这个功能用于满足资产发行的合规要求。

另外系统还支持黑名单功能,但本教程里不包含黑名单的具体介绍。


【教程内容】

假设你有一个资产 NEWASSET ,要设置白名单。

1,通过命令行获取资产的详细属性设置

命令格式:
Code: [Select]
get_asset [资产代码]

示例:
Code: [Select]
unlocked >>> get_asset NEWASSET
get_asset NEWASSET
{
  "id": "1.3.123",
  "symbol": "NEWASSET",
  "precision": 4,
  "issuer": "1.2.695",
  "options": {
    "max_supply": "1000000000000",
    "market_fee_percent": 0,
    "max_market_fee": 0,
    "issuer_permissions": 79,
    "flags": 2,
    "core_exchange_rate": {
      "base": {
        "amount": 100000,
        "asset_id": "1.3.0"
      },
      "quote": {
        "amount": 10000,
        "asset_id": "1.3.123"
      }
    },
    "whitelist_authorities": [],
    "blacklist_authorities": [],
    "whitelist_markets": [],
    "blacklist_markets": [],
    "description": "{\"main\":\"\",\"market\":\"TEST\"}",
    "extensions": []
  },
  "dynamic_asset_data_id": "2.3.123"
}

在上述结果中,

"issuer_permissions": 79 表示该资产的白名单启用状态是否可以修改。
实际上, issuer_permissions 是资产多个权限参数的集合,将 issuer_permissions 转为二进制,从右边数第 2 位表示白名单,如果是 1 则为可修改,是 0 则为不可修改。

"flags": 2 表示已经启用了白名单。
实际上,flags是资产多个旗标参数的集合,将 flags 转为二进制,从右边数第 2 位表示白名单,如果是 1 则为开启,是 0 则为关闭。

"whitelist_authorities": [] 表示没有设置具体名单,这时,白名单功能不生效(结果可测试)。
实际上, whitelist_authorities 里设置的是“白名单管理员”名单,而不是白名单本身。这样的设计很灵活,可以指定多个管理员,修改名单不一定要使用发行者账号,不需要频繁修改资产参数。


2,开启白名单功能

 1) 可以在GUI里修改资产的“旗标”设置开启白名单。
    不过需要注意,如果在命令行设置过资产参数,则不要在 GUI 进行操作,以免导致问题。

 2) 通过命令行开启或关闭资产白名单
    先将 flags 二进制里相应位置修改为1或0,然后转为十进制,执行 upate_asset 命令。可以和下面步骤合并,具体在下面会介绍。


3,将管理员账号加入白名单管理员名单

比如,你要将 newaccount1 设置为 NEWASSET 的白名单管理员。

3.1 首先要知道 newaccount1 的 ID,这个 ID 可以通过GUI的浏览账号功能或者命令行 get_account 命令取到。命令格式:
Code: [Select]
get_account [账户名]

示例:
Code: [Select]
unlocked >>> get_account newaccount1
get_account newaccount1
{
  "id": "1.2.695",
  ...
}
上面结果显示, newaccount1 的 ID 是 1.2.695

3.2 然后,将上述 get_asset 命令获取的结果中 "options" 后的花括号里面的内容合成一行,再将 "1.2.695" 加入到 whitelist_authorities 后面的方括号中,比如(包含方括号) ["1.2.695"],执行 update_asset 命令。如果有多个管理员,则一起放入方括号中,使用逗号分隔,比如 ["1.2.695","1.2.696"] 。
命令格式:
Code: [Select]
update_asset [资产代码] [新发行人] [新资产参数] [是否广播]

示例:
Code: [Select]
update_asset NEWASSET null {"max_supply":"1000000000000","market_fee_percent": 0,"max_market_fee": 0,"issuer_permissions": 79,"flags": 2,"core_exchange_rate": {"base": {"amount": 100000,"asset_id":"1.3.0" },"quote": {"amount": 10000,"asset_id":"1.3.123" } },"whitelist_authorities": ["1.2.695"],"blacklist_authorities": [],"whitelist_markets": [],"blacklist_markets": [],"description":"{\"main\":\"\",\"market\":\"TEST\"}","extensions": []} true

其中,
第 1 个参数 NEWASSET 是资产代码;
第 2 个参数 null 表示不修改资产发行人(如果要把资产转给名叫 null 的账户,请使用引号,比如 "null")
第 3 个参数,花括号 {} 里是新的资产参数, 由前面得到的 options 加入一个管理员账号后得出。如果同时需要启用白名单,则修改 flags 后面的数值。
第 4 个参数 true 表示执行,如果填 false 表示对命令格式进行测试,不会执行

命令执行完成后,可以使用 get_asset 命令重新查看资产白名单管理员是否已经设好

注意:
 1) update_asset 命令的第 3 个参数会将资产的所有属性设置完全覆盖,所以务必仔细检查,使用完整数据。
    比如要删掉某个管理员,必须在参数中指定所有其他管理员。
 2) 使用命令行设置后,不要再用 GUI 来修改资产属性,因为 GUI 目前不支持白名单设置,通过 GUI 操作可能导致数据丢失


4. 管理员管理白名单

现在管理员 newaccount1 可以管理资产 NEWASSET 的白名单了。默认名单是空,也就是说现在没人可以对该资产进行转账、交易等操作(可测试)。

4.1 查询白名单
这里有个问题:我使用的命令行有个 BUG ,导致不显示管理员设置的具体名单。如果 BUG 修复,可以使用 get_account 命令查看当前设置的白名单。

示例:
Code: [Select]
unlocked >>> get_account newaccount1
get_account newaccount1
{
  ...
  "whitelisting_accounts": [],
  "blacklisting_accounts": [],
  "whitelisted_accounts": [],
  "blacklisted_accounts": [],
  ...
}
其中 whitelisted_accounts 就是当前管理员设置的白名单。
另外 whitelisting_accounts 表示有哪个人把当前账号加入了他自己的白名单。

4.1 修改白名单
使用 whitelist_account 命令可以将账号加入白名单,或者从白名单移除。命令格式:
Code: [Select]
whitelist_account [操作人账号] [操作对象账号] [增加或删除] [是否广播]

示例1(加入白名单):
Code: [Select]
unlocked >>> whitelist_account newaccount1 newaccount2 true false

上述命令是将 newaccount2 加入 newaccount1 的白名单,需要 newaccount1 的权限才能执行。
执行完成后,使用 get_account 命令查看是否生效:

Code: [Select]
unlocked >>> get_account newaccount2
get_account newaccount2
{
  ...
  "whitelisting_accounts": [
    "1.2.695"
  ],
  "blacklisting_accounts": [],
  "whitelisted_accounts": [],
  "blacklisted_accounts": [],
  ...
}
可以看到, newaccount2 已经在 1.2.695 也就是 newaccount1 的白名单里了。因为 newaccount1 是 NEWASSET 资产的白名单管理员,这时 newaccount2 可以正常使用 NEWASSET 资产。

注意:
当资产设置了白名单管理人后,管理员、甚至发行人自己,如果需要使用该资产,也需要先加入白名单。

示例2(从白名单移除):
Code: [Select]
unlocked >>> whitelist_account newaccount1 newaccount2 false false
上述命令是将 newaccount2 从 newaccount1 的白名单移除,需要 newaccount1 的权限才能执行。
用户从白名单移除后,即使持有资产,也不能转出或者卖出。


99
不好意思,没时间多写。

问题描述在 https://github.com/cryptonomex/graphene/issues/645 最近几天已经在BTS和MUSE网络中出现多次,影响严重。

BTS 见证人请打我发布的这个补丁:  https://github.com/abitmore/bitshares-2/commit/2cf8fb62c98befb70fedffe739a05bc4ac5a0de8
该补丁不涉及硬分叉,只是丢弃有问题的块(可以理解为软分叉)。

补丁使用方法:
Code: [Select]
...
git checkout v2.0.160328

# 把这几行加到 `git checkout v2.0.160328` 之后, `make` 之前,重新编译
git remote add abit https://github.com/abitmore/bitshares-2.git
git fetch abit
git merge -m "Merge abit/fix-645-block-timestamp" abit/fix-645-block-timestamp

git submodule update --init --recursive
...

MUSE见证人请检查 Telegram 消息。

// 更新:官方 Github 最新 master / Release 已经包含这个补丁,无需单独打补丁了。

100
General Discussion / Serious network issue around 2016-07-29T21:20:00
« on: July 30, 2016, 10:34:39 pm »
Wanted to write more about this issue last night, but didn't get time. Still no much time now.

The issue is described in https://github.com/cryptonomex/graphene/issues/645, which has been triggered in BitShares network and MUSE network several times recently.

BitShares witnesses please apply this patch, if not already done: https://github.com/abitmore/bitshares-2/commit/2cf8fb62c98befb70fedffe739a05bc4ac5a0de8

MUSE witnesses please check Telegram channel for more info.

Code: [Select]
...
git checkout v2.0.160328

# add these lines after `git checkout v2.0.160328` and before `make`
git remote add abit https://github.com/abitmore/bitshares-2.git
git fetch abit
git merge -m "Merge abit/fix-645-block-timestamp" abit/fix-645-block-timestamp

git submodule update --init --recursive
...

101
On BitShares network.
Code: [Select]
2016-07-09T21:00:03 th_a:invoke handle_block         handle_block ] Got block: #7723323 time: 2016-07-09T21:00:03 latency: 346 ms from: spectral  irreversible: 7723304 (-19)                   application.cpp:521
2016-07-09T21:00:11 th_a:invoke handle_block         handle_block ] Got block: #7723323 time: 2016-07-09T21:00:00 latency: 11829 ms from: verbaltech2  irreversible: 7723305 (-18)                      application.cpp:521
2016-07-09T21:00:15 th_a:invoke handle_block         handle_block ] Got block: #7723324 time: 2016-07-09T21:00:15 latency: 63 ms from: verbaltech2  irreversible: 7723305 (-19)                 application.cpp:521
2016-07-09T21:00:15 th_a:invoke handle_block         handle_block ] Got block: #7723324 time: 2016-07-09T21:00:15 latency: 227 ms from: roadscape  irreversible: 7723305 (-19)                  application.cpp:521
2016-07-09T21:00:24 th_a:invoke handle_block         handle_block ] Got block: #7723325 time: 2016-07-09T21:00:24 latency: 199 ms from: delegate.btsnow  irreversible: 7723305 (-20)                    application.cpp:521
2016-07-09T21:00:24 th_a:invoke handle_block         handle_block ] Got block: #7723325 time: 2016-07-09T21:00:24 latency: 713 ms from: delegate-clayop  irreversible: 7723305 (-20)                    application.cpp:521
2016-07-09T21:00:30 th_a:invoke handle_block         handle_block ] Got block: #7723326 time: 2016-07-09T21:00:30 latency: 309 ms from: abc123  irreversible: 7723305 (-21)                     application.cpp:521
2016-07-09T21:00:30 th_a:invoke handle_block         handle_block ] Got block: #7723326 time: 2016-07-09T21:00:30 latency: 397 ms from: datasecuritynode  irreversible: 7723307 (-19)                   application.cpp:521
2016-07-09T21:00:33 th_a:invoke handle_block         handle_block ] Got block: #7723327 time: 2016-07-09T21:00:33 latency: 142 ms from: dele-puppy  irreversible: 7723307 (-20)                 application.cpp:521
2016-07-09T21:00:33 th_a:invoke handle_block         handle_block ] Got block: #7723327 time: 2016-07-09T21:00:33 latency: 252 ms from: bue  irreversible: 7723305 (-22)                        application.cpp:521
2016-07-09T21:00:39 th_a:invoke handle_block         handle_block ] Got block: #7723328 time: 2016-07-09T21:00:39 latency: 387 ms from: fox  irreversible: 7723305 (-23)                        application.cpp:521
2016-07-09T21:00:42 th_a:invoke handle_block         handle_block ] Got block: #7723329 time: 2016-07-09T21:00:42 latency: 149 ms from: spartako  irreversible: 7723308 (-21)                   application.cpp:521
2016-07-09T21:00:45 th_a:invoke handle_block         handle_block ] Got block: #7723330 time: 2016-07-09T21:00:45 latency: 156 ms from: rnglab  irreversible: 7723309 (-21)                     application.cpp:521
2016-07-09T21:00:48 th_a:invoke handle_block         handle_block ] Got block: #7723331 time: 2016-07-09T21:00:48 latency: 152 ms from: mr.agsexplorer  irreversible: 7723309 (-22)                     application.cpp:521
2016-07-09T21:00:51 th_a:invoke handle_block         handle_block ] Got block: #7723332 time: 2016-07-09T21:00:51 latency: 407 ms from: delegate.baozi  irreversible: 7723309 (-23)                     application.cpp:521
2016-07-09T21:00:54 th_a:invoke handle_block         handle_block ] Got block: #7723333 time: 2016-07-09T21:00:54 latency: 93 ms from: datasecuritynode  irreversible: 7723309 (-24)                    application.cpp:521
2016-07-09T21:00:54 th_a:invoke handle_block         handle_block ] Got block: #7723333 time: 2016-07-09T21:00:54 latency: 93 ms from: datasecuritynode  irreversible: 7723309 (-24)                    application.cpp:521
2016-07-09T21:00:57 th_a:invoke handle_block         handle_block ] Got block: #7723334 time: 2016-07-09T21:00:57 latency: 54 ms from: verbaltech2  irreversible: 7723311 (-23)                 application.cpp:521
2016-07-09T21:01:00 th_a:invoke handle_block         handle_block ] Got block: #7723335 time: 2016-07-09T21:01:00 latency: 184 ms from: spectral  irreversible: 7723312 (-23)                   application.cpp:521

102
中文(Chinese) / Worker制度改进建议
« on: June 18, 2016, 12:13:38 pm »
1. 所有worker工资发放,必须由worker发起人提出申请,经过理事会同意。具体可以采用多重签名方式,不需要修改代码。参考 https://cryptofresh.com/u/bsip10-worker

由于理事会成员是股东投票决定,相对公正,适合最后把关做成果审核,避免有人申请的活没干好就拿钱。

具体可以按里程碑/工作进展情况,分批领取工资。

2. 保障申请成功的worker能领到工资,现在投票、撤票比较随意,对申请人工作积极性影响比较大,进而导致工作效率问题,甚至导致工作无法完成。这个可能要改代码,具体规则待讨论。

103
中文(Chinese) / MetaExchange 停运 MetaFees 回购,请注意
« on: June 02, 2016, 10:18:48 am »
英文帖子在这里 https://bitsharestalk.org/index.php/topic,22580.0.html

内盘 Open.BTC:METAFEES 交易对有回购。

当初众筹价格是0.02BTC一个METAFEES,回购价格0.027。

其他METAEX资产请尽快提现。

104
General Discussion / !!!CAUTION!!! All public seed nodes down??
« on: May 04, 2016, 10:08:42 am »
Someone is attacking BitShares? Or bug?

Code: [Select]
1535394ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 83.221.132.47:1776
1541939ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 188.40.91.213:1776
1541939ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 114.92.236.175:62015
1556942ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 71.197.2.119:1776
1561942ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 45.32.247.234:1776
1567965ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 82.211.31.175:1776
1571306ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 159.203.15.153:1776
1572544ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 188.166.188.206:1776
1573421ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 107.170.245.89:1777
1573421ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 54.85.252.77:39705
1573421ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 104.236.144.84:1777
1573421ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 40.127.190.171:1777
1573421ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 185.25.22.21:1776
1573422ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 23.95.43.126:50696
1573422ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 109.73.172.144:50696
1573422ms th_a       application.cpp:177           reset_p2p_node       ] Adding seed node 128.199.143.47:2015

Code: [Select]
~$ telnet 83.221.132.47 1776
Trying 83.221.132.47...
^C
~$ telnet 188.40.91.213 1776
Trying 188.40.91.213...
telnet: Unable to connect to remote host: Connection refused
~$ telnet 71.197.2.119 1776
Trying 71.197.2.119...
telnet: Unable to connect to remote host: Connection refused
~$ telnet 45.32.247.234 1776
Trying 45.32.247.234...
telnet: Unable to connect to remote host: Connection refused
~$ telnet 82.211.31.175 1776
Trying 82.211.31.175...
telnet: Unable to connect to remote host: Connection refused
~$ telnet 159.203.15.153 1776
Trying 159.203.15.153...
telnet: Unable to connect to remote host: Connection refused
~$ telnet 188.166.188.206 1776
Trying 188.166.188.206...
telnet: Unable to connect to remote host: Connection refused
~$ telnet 107.170.245.89 1777
Trying 107.170.245.89...
Connected to 107.170.245.89.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
~$ telnet 54.85.252.77 39705
Trying 54.85.252.77...
^C
~$ telnet 104.236.144.84 1777
Trying 104.236.144.84...
^C
~$ telnet 40.127.190.171 1777
Trying 40.127.190.171...
^C
~$ telnet 185.25.22.21 1776
Trying 185.25.22.21...
^C
~$ telnet 23.95.43.126 50696
Trying 23.95.43.126...
^C
~$ telnet 109.73.172.144 50696
Trying 109.73.172.144...
^C
~$ telnet 128.199.143.47 2015
Trying 128.199.143.47...
telnet: Unable to connect to remote host: Connection refused

After found it's not responding, I just restarted my seed node. A working seed node should respond like this:

Code: [Select]
~$ telnet 114.92.236.175 62015
Trying 114.92.236.175...
Connected to 114.92.236.175.
Escape character is '^]'.
]▒▒a▒X
      ▒o▒▒▒g▒▒s▒a▒Z▒f▒^]

105
中文(Chinese) / 这个内盘跨资产搬砖机器人很牛逼
« on: May 01, 2016, 12:06:09 pm »
http://cryptofresh.com/u/ar8173r

比如 http://cryptofresh.com/tx/56f4d10d26bcbb977770ad97d61e61673ec3f596 一单净赚1.3METAFEES

一天N单

谁做的,站出来?  [member=30068]botfund[/member] 是你吗?


Pages: 1 2 3 4 5 6 [7] 8 9 10 11 12 13 14