0 Members and 1 Guest are viewing this topic.
Ok, so I guess there's not much point to running blocks and script on different machines then... it's more a question of protecting the delegate block production environment by not revealing owner keys?I'm gonna take the opportunity to read up on owner keys, active keys and sign keys. I found a couple of your guides on the subject, i will follow these.https://bitsharestalk.org/index.php?topic=14344.0https://bitsharestalk.org/index.php?topic=14360.0Thanks for the help!
Quote from: Spectral on July 29, 2015, 06:29:17 pmI'm trying to run the script connecting to a wallet that is not the wallet of the delegate. The wallet has a 50BTS balance right now, so that should be enough.So it seem your delegate is "running" on a different machine then?
I'm trying to run the script connecting to a wallet that is not the wallet of the delegate. The wallet has a 50BTS balance right now, so that should be enough.
QuoteDoes it mean that the script must connect to the delegate wallet itself and draw funds from that? If so, how can I do that without providing the delegate wallet password in cleartext in 'config.py'?If you want to provide continuous updates for the feed, then you can only put the password in cleartext into the config. BUT, you should create a wallet that only contains the most recent active key and signing key of the delegate in it .. and no other account ...Then you can do a rescan of the blockchain to catch up with the balance and run the script again
Does it mean that the script must connect to the delegate wallet itself and draw funds from that? If so, how can I do that without providing the delegate wallet password in cleartext in 'config.py'?
Update required! Forcing now!Unlocking walletpublishing feeds for delegate: bitspace-clainsTraceback (most recent call last): File "main.py", line 473, in <module> update_feed(rpc,asset_list_final) File "main.py", line 273, in update_feed result = rpc.wallet_publish_feeds(delegate, assets) File "/home/manuel/.local/lib/python3.4/site-packages/bitsharesrpc/client.py", line 135, in method "id": 0 File "/home/manuel/.local/lib/python3.4/site-packages/bitsharesrpc/client.py", line 78, in rpcexec raise RPCError(ret['error']['detail'])bitsharesrpc.client.RPCError: 20010 insufficient_funds: insufficient funds {"from_account_name":"bitspace-clains","amount_to_withdraw":{"amount":50000,"asset_id":0},"balance_records":[]} th_a wallet.cpp:68 withdraw_to_transaction
You've started a rewrite. Good.However without test network for bitshares 2.0 it looks impractical, doesn't it ?
Quote from: xeroc ¯\_(ツ)_/¯ on June 08, 2015, 05:55:16 pmQuote from: emski on June 08, 2015, 05:28:03 pmMost of the changes I've made in this script modification are now merged in xeroc's script.There is no need to support this mod anymore.Maybe you want to join python development?I can definitely need your help!I'll be happy to help whenever I can.
Quote from: emski on June 08, 2015, 05:28:03 pmMost of the changes I've made in this script modification are now merged in xeroc's script.There is no need to support this mod anymore.Maybe you want to join python development?I can definitely need your help!
Most of the changes I've made in this script modification are now merged in xeroc's script.There is no need to support this mod anymore.
I've pushed an update fixing the issue with yahoo.Thanks xeroc for the support.I was away snowboarding in the alps without reliable internet access.I'll post some more updates when I'm able to catch up with all the events.
xeroc, why does your script lock the wallet after updating feed? the delegate needs an unlocked wallet to run?
i'd guess you have installed prettytable into python2 .. maybe there ia a separate pip3 or so for python3 .. else you can try easy_install3 .. dependa on your linux distribution ..
I'm getting a "unknown error - yahoo" now when I run the script. Anyone else getting this?
You need python3!!
Oh .. you run the script with python main.py ALL Will publish all prices implemented in the script I certainly have to do more documentation on ALL my scripts .. give me some time please
Quote from: kokojie on March 13, 2015, 02:33:24 pmI'm getting a "unknown error - yahoo" now when I run the script. Anyone else getting this?I made some modifications and moved the script into bitshares-pytools on github .. please try that version
EDIT: Just to note that currently bter returns an error so it is ignored by the script anyway
I recommend every delegate to set bter_trust_level to 0.0 in the config file
Quote from: emski on January 06, 2015, 02:13:51 pmI've pushed an update fixing Poloniex's asset name change.same here ... i should open up my own thread for updates and not misuse yours
I've pushed an update fixing Poloniex's asset name change.
Quote from: clayop on December 13, 2014, 02:27:33 amCan you add KRW to your script? There is a growing interest in BitKRW and I want to introduce Korean community how to use it. (Plus encouraging Korean exchanges to add BitKRW)Done! I didn't realise how much feed it already got. Also I see a lot of new markets were enabled recently. I'm updating my feeds so that I publish feed for each active market (and KRW as it currently has 49 feeds).
Can you add KRW to your script? There is a growing interest in BitKRW and I want to introduce Korean community how to use it. (Plus encouraging Korean exchanges to add BitKRW)
I was talking about how it was updating every single block. You're just wasting your own money if most delegates do it much less often.
I'll stop it for some brief investigation.
Is this script spamming feed updates right now?http://bitsharesblocks.com/blocks/block?id=1248105
Think we need an update to handle the new date format, "oldtime" is no longer parsed correctly. This seems to work but I'm not 100% sure:Code: [Select]oldtime[ f[ "asset_symbol" ] ] = datetime.strptime(f["last_update"],"%Y-%m-%dT%H:%M:%S")
oldtime[ f[ "asset_symbol" ] ] = datetime.strptime(f["last_update"],"%Y-%m-%dT%H:%M:%S")
Quote from: kokojie on November 15, 2014, 01:14:24 amcool, emski yours is working for me nowThe error in xeroc's script you see might be related to improper config file.There are different variables in both versions. Make sure you use proper version.
cool, emski yours is working for me now
{ "bts_rpc": { "url": "http://10.0.0.16:19988/rpc", "username": "" "password": "" }, "delegate_list": [ "delegate.xeroc"], "payaccount" : "delegate.xeroc", "maxAgeFeedInSeconds" : 2700, "minValidAssetPrice" : 0.00001, "discount" : 0.995, "change_min" : 0.5, "btc38_trust_level" : 0.7, "bter_trust_level" : 1.0, "poloniex_trust_level" : 0.5, "bittrex_trust_level" : 0.5 }
I still get errors with both emski and xeroc's updated script:emski: File "./btsx_feed.py", line 125 volume_in_btc[ mapAsset ].append(float(result[coin.lower()+"_btc"]["vol_btc"])*confi$ ^SyntaxError: invalid syntaxxeroc: File "/home/user/feed_xeroc/btsx_feed.py", line 433, in <module> if publish_rule() : File "/home/user/feed_xeroc/btsx_feed.py", line 47, in publish_rule elif fabs(myCurrentFeed[asset]-realPrice[asset])/realPrice[asset] > config["change_min"] and\KeyError: 'change_min'
Apparently BTER changed BTSX asset name to BTS.I've pushed a quick patch to address that.I'll try to make something more robust soon.
I think there might be an error in discount implementation in the original script.It increases the feed price instead of decreasing it.assume discount = 0.995Original code:Code: [Select]### Discount price_in_btsx_weighted[asset] = price_in_btsx_weighted[asset] / config["discount"]My code:Code: [Select]### Discount price_in_btsx_weighted[asset] = price_in_btsx_weighted[asset] * config["discount"]
### Discount price_in_btsx_weighted[asset] = price_in_btsx_weighted[asset] / config["discount"]
### Discount price_in_btsx_weighted[asset] = price_in_btsx_weighted[asset] * config["discount"]
I as a user/owner have always advocated for weighing the price feed from different exchanges, so I am happy to see that and hope more delegates will start using this script.The other features seem beneficial to the delegates themselves, so I hope for a fast adoption.0.02 BTSX