BitShares Forum
Main => Stakeholder Proposals => Topic started by: eagleeye on June 08, 2015, 06:44:51 pm
-
58 delegates have now updated, thank you so much.
Start trading
The Shenzhen composite moves 2%+ in either direction a day.
-
Just in time for those markets to start dropping?
:)
-
Just in time for those markets to start dropping?
:)
Lol... But seriously, this could be epic - a true blockchain world first.
-
The number of feeds seems to have dropped to 45 for all new Indexes
51 are needed, correct?
-
The number of feeds seems to have dropped to 45 for all new Indexes
51 are needed, correct?
Yes, so until we get back up to 51, no shorting is possible.
-
51 delegates have now updated, thank you so much.
Let's see if anyone will trade this stuff. The Shenzhen composite moves 2%+ in either direction a day.
Once these start working it might be a good idea to get them put on the Chinese exchanges.
-
Bump we lost 6 gained 2 back
-
http://vote.bunkermining.com and we can get 5 more! :)
Within the hour delegate.rgcrypto will also be publishing these feeds.
-
Confirmed.. publishing feeds now: http://bitsharesblocks.com/delegate/feeds?name=delegate.rgcrypto
-
In spite of the turmoil in my head (lots of things to process from bitshares 2.0! ;) ), I managed to work more on the feeds and I now have all 5 market indices (including SHANGHAI) working reliably.
The feeds are fetched simultaneously from Yahoo, Google and Bloomberg and use the average of the three. That means that if one of them goes down, we still get the info from the other two.
I also implemented a (very basic) system that warns you in the logs if the prices are not consistent between all the sources.
So for people using the bts_tools, please upgrade to the latest 0.2.8 version to get those running. Let's get those markets open!
-
scrapping prices from google finance is against their TOS .. it may lead to trouble .. please read the TOS!
-
scrapping prices from google finance is against their TOS .. it may lead to trouble .. please read the TOS!
Is this relevant?
http://scrape-google-finance.compunect.com/
-
3 delegates more needed at 48
-
Vote in some standby delegates
-
Good work eagleeye.
-
FYI
The following delegates will be removed from my slate this weekend if they don't start actively publishing feeds.
dev.nathanhourt.com
developer.vikram
elmato
martin-38ptswarrior-raum
btsx.chinesecommunity
del.fav
del0.cass
dev-pc.bitcube
-
Good... with BTS 2.0 still being far away I think it is critical that all delegates publish price feeds. Even if it is just manually twice a day.
-
FYI
The following delegates will be removed from my slate this weekend if they don't start actively publishing feeds.
dev.nathanhourt.com
developer.vikram
elmato
martin-38ptswarrior-raum
btsx.chinesecommunity
del.fav
del0.cass
dev-pc.bitcube
I was recently wondering why developers weren't publishing feeds and I concluded it must be a legal issue of some sort.
-
FYI
The following delegates will be removed from my slate this weekend if they don't start actively publishing feeds.
dev.nathanhourt.com
developer.vikram
elmato
martin-38ptswarrior-raum
btsx.chinesecommunity
del.fav
del0.cass
dev-pc.bitcube
I was recently wondering why developers weren't publishing feeds and I concluded it must be a legal issue of some sort.
for a couple of weeks some stated they wanted to code their own feed script....
-
I was recently wondering why developers weren't publishing feeds and I concluded it must be a legal issue of some sort.
If you are just "signing blocks," it's clear you are a "miner."
Once you start injecting information, especially commodities and foreign currencies, it isn't so cut and dry. Posting feeds may not be against regulations, it just isn't 100% clear either way.
-
In spite of the turmoil in my head (lots of things to process from bitshares 2.0! ;) ), I managed to work more on the feeds and I now have all 5 market indices (including SHANGHAI) working reliably.
The feeds are fetched simultaneously from Yahoo, Google and Bloomberg and use the average of the three. That means that if one of them goes down, we still get the info from the other two.
I also implemented a (very basic) system that warns you in the logs if the prices are not consistent between all the sources.
So for people using the bts_tools, please upgrade to the latest 0.2.8 version to get those running. Let's get those markets open!
Please get that github updated so we can!!!!
You haven't committed your changes. Please do that before you make announcements! Also, be sure you update the python package too so we can install it with pip install --upgrade.
Thanks!
-
Vote for martin-38ptswarrior-raum and you will have one more... he is really close !
Sent from my ALCATEL ONE TOUCH 997D
-
Good work eagleeye.
Thank you Fuzzy
We are now at 49 delegates
-
Please get that github updated so we can!!!!
oops sorry, it was very late and forgot to push :-[ This is fixed now. I did release it on pypi though, so "pip install --upgrade" would have worked, but you're right, I should be more careful.
I did want to get this out as soon as possible while this is still a hot topic, to make sure to take advantage that people are paying attention and to get those markets open.
I also wanted to thank eagleeye for pushing this issue. Even though those markets won't have a lot of depth at the beginning, I think it is important to be able to say that the markets are open and waiting for traders. I do believe that those markets are important for BitShares as they emphasize very clearly that BitAssets can track anything, not only fiat currencies but pretty much anything where people agree on what the name means. This is a crucial point, I believe, and it is much easier to show people that they can buy or sell NASDAQC, for instance, than trying to explain how it works.
-
scrapping prices from google finance is against their TOS .. it may lead to trouble .. please read the TOS!
well, they used to have it clearly specified in their old TOS (see: http://www.google.com/policies/terms/archive/20070416-20120301/, they removed §5.3 about scraping), but in the new version, the language is much fuzzier:
Don’t misuse our Services. For example, don’t interfere with our Services or try to access them using a method other than the interface and the instructions that we provide.
It's not so clear to me anymore that scraping is explicitly forbidden here, but IANAL so don't take my word for it.
The other thing is that using google as a feed provider in the bts_tools entails fewer than 10 requests/hour, which is so low it will certainly not be detected or banned (although the pattern of querying clearly indicates scraping).
But you're right, this still feels a bit in a legal gray zone, so I'll make it configurable in the bts_tools which feed providers the delegate wants to use.
-
Please get that github updated so we can!!!!
oops sorry, it was very late and forgot to push :-[ This is fixed now. I did release it on pypi though, so "pip install --upgrade" would have worked, but you're right, I should be more careful.
I did want to get this out as soon as possible while this is still a hot topic, to make sure to take advantage that people are paying attention and to get those markets open.
I also wanted to thank eagleeye for pushing this issue. Even though those markets won't have a lot of depth at the beginning, I think it is important to be able to say that the markets are open and waiting for traders. I do believe that those markets are important for BitShares as they emphasize very clearly that BitAssets can track anything, not only fiat currencies but pretty much anything where people agree on what the name means. This is a crucial point, I believe, and it is much easier to show people that they can buy or sell NASDAQC, for instance, than trying to explain how it works.
I haven't checked since I posted my msg here, but I DID use the pip method to upgrade, but it only found 0.2.6. THEN I went to github and it was 5 days old.
If you truly did update pypi then the issue must be host caching, b/c it definitely thought 0.2.6 was the most recent version. Now that it's up on github I will update the files that changed manually.
UPDATE: Confirmed- local machine is fine but vps still only gets the 0.2.6 version. I obtained the feeds update directly from github.
-
If you truly did update pypi then the issue must be host caching, b/c it definitely thought 0.2.6 was the most recent version. Now that it's up on github I will update the files that changed manually.
UPDATE: Confirmed- local machine is fine but vps still only gets the 0.2.6 version. I obtained the feeds update directly from github.
it was released on pypi, see: https://pypi.python.org/pypi/bts_tools/
sometimes pip gets mixed up with versions, so a way to upgrade a package that works everytime is to do "pip uninstall bts_tools && pip install bts_tools", maybe that'll solve your issues.
-
Bump we still need just 2 more.
Please update your feeds, this is ridiculous we need this up.
-
Have you tried PMing the delegates that arent publishing?
-
Have you tried PMing the delegates that arent publishing?
Ive PMedmodt of the ones with 19 feeds. I don't remember if I PMed the developer team as they don't show feeds.
-
Delegates without feeds have been removed from my slate.
Support the system. Do your bit for bitshares!
-
Delegates without feeds have been removed from my slate.
Support the system. Do your bit for bitshares!
Wow.. nicely done.
Imagine if more people voted with this in mind.
Sure glad all my http://vote.bunkermining.com delegates are always up to date and have feeds. :)
-
I just migrated to xeroc (thanks!) script for publishing feed of my tre active delegates: spartako, spartako1, spartako2
so now we have 52 feeds for new indexes :)
-
I just migrated to xeroc (thanks!) script for publishing feed of my tre active delegates: spartako, spartako1, spartako2
so now we have 52 feeds for new indexes :)
+5% Lets start shorting ;)
Which one first?
-
I went for NASDAQC - Greece should make it a bit more fun ;)
-
I just migrated to xeroc (thanks!) script for publishing feed of my tre active delegates: spartako, spartako1, spartako2
so now we have 52 feeds for new indexes :)
Once i am back from vacation I will evaluate scrapping google finance and bloomberg like wackou does already to get a better decentralization of sources ..
-
Bump we are now fully functioning
-
Bump we are now fully functioning
Then send all those traders you talked about ! :)
-
Can the Precision be changed on these assets?
I think the system took my canceled sell order as yield as it was only 0.01 NASDAQC.
Now the yield is 100% ???
-
Transaction Fee to Cover Short Position is also 0.01 BitNASDAQC - currently 7,400.36 BTS
I haven't thought this through :(
-
Transaction Fee to Cover Short Position is also 0.01 BitNASDAQC - currently 7,400.36 BTS
I haven't thought this through :(
Oh dear.
Is it possible to change the parameters of an MPA?
-
Transaction Fee to Cover Short Position is also 0.01 BitNASDAQC - currently 7,400.36 BTS
I haven't thought this through :(
Oh dear.
Is it possible to change the parameters of an MPA?
This is paramount in importance.
-
Transaction Fee to Cover Short Position is also 0.01 BitNASDAQC - currently 7,400.36 BTS
I haven't thought this through :(
yup same for me .. as i tested it today …:(
-
I don't think it's possible to update the parameters of an MPA - the only things we can do:
*) update the scripts to price it lower (directly in BTS, say, or just 1000 x lower in CNY)
*) create new MPAs with better parameters
-
I don't think it's possible to update the parameters of an MPA - the only things we can do:
*) update the scripts to price it lower (directly in BTS, say, or just 1000 x lower in CNY)
*) create new MPAs with better parameters
Which is the simplest option to get everyone trading?
-
Which is the simplest option to get everyone trading?
They both have the same complexity because you have to get all the delegates to update their scripts again either way. Here are some pros/cons:
new MPAs
Cons:
* Cost of registration for new MPA names is 5000 BTS / name
* Redundency - the first set of MPAs will continue to exist, with the better names, since the new ones would need to be unique
Pros:
* Can keep the CNY 1:1 pricing
price in BTS
Cons:
* Prices will be less familiar to the chinese traders if a /CNY market becomes available
Pros:
* Cheap to do
* Purity of pricing in BTS, just like the other MPAs
Scale existing CNY pricing down by 1000 (or some other number)
Cons:
* Prices will be unfamiliar to the chinese traders
* Feels dirty
Pros:
* Cheap to do
We're a little bit stuck between a rock and a hard place here...
-
It looks like this is turning out to be a missed opportunity if we cant get a quick consensus.
Everyone seems to be more interested in bitshares 1 v bitshares 2 threads.
-
In bts 2 .. we can simple vote for a hard fork to fix this!
-
In bts 2 .. we can simple vote for a hard fork to fix this!
I would prefer the quick dirty method as bts 2 could take alot more time than you think!
-
In bts 2 .. we can simple vote for a hard fork to fix this!
I would prefer the quick dirty method as bts 2 could take alot more time than you think!
I know that you can change some attributes for UIA if current supply is zero .. maybe something similar is possible with mia .. though i dont know if there is a "owner" for mias
-
wallet_uia_update_supply <paying_account> <asset_symbol> <max_supply_with_trailing_decimals>
for a MIA
-
serious school boy error and the first time Bitshares has actually pissed me off >:(
All of these INDEXES are untradable and I'm in for quite a few BTS
TIMESTAMP BLOCK FROM TO AMOUNT MEMO BALANCE FEE ID
================================================================================================================================================================================================
|2015-06-14T16:18:10 2802474 SHORT-9d1b797e MARGIN-9d1b797e 14,751.00000 BTS add collateral 0.00000 BTS 0.00000 BTS VIRTUAL |
| MARKET MARGIN-9d1b797e 7,375.50000 BTS add collateral 0.00000 BTS |
| MARGIN-9d1b797e MARKET 0.01 NASDAQC short proceeds @ 0.000001356502887 NASDA... 0.00 NASDAQC |
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|2015-06-14T16:18:10 2802474 ASK-da8f10e1 MARKET 7,375.50000 BTS fill ask @ 0.000001356502887 NASDAQC / BTS 0.00000 BTS 0.00000 BTS VIRTUAL |
| ASK-da8f10e1 mulla 0.01 NASDAQC ask proceeds @ 0.000001356502887 NASDAQC... 0.01 NASDAQC |
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2015-06-14T19:16:30 2803543 mulla BID-2598e19e 0.01 NASDAQC buy BTS @ 0.00000125 NASDAQC / BTS 0.00 NASDAQC 0.10000 BTS ad260c3d
2015-06-15T10:13:18 2808911 BID-2598e19e mulla 0.01 NASDAQC cancel BID-2598e19e 0.01 NASDAQC 0.01 NASDAQC fafe4e2f
-
Ok, so we need everyone to update the script, monsterer?
-
Ok, so we need everyone to update the script, monsterer?
We need to chose how we will update the script first :)
-
Ok, so we need everyone to update the script, monsterer?
We need to chose how we will update the script first :)
I feel we just go to 10000th or so 0.00001 or what you were thinking
We already have iHashFury in for some BTS so I don't think we should sacrifice him, we just need to make it go lower.
-
Sure, 1/1000 seems like a reasonable scaling factor - I was leaning more towards pricing in BTS, actually... we could do with some more input on the matter.
Once we are sure which way to go, we need the feed authors to update their scripts for us...
-
Sure, 1/1000 seems like a reasonable scaling factor - I was leaning more towards pricing in BTS, actually... we could do with some more input on the matter.
Once we are sure which way to go, we need the feed authors to update their scripts for us...
I would like to hear iHashFurys input, we may need to go to 1/10000 or 1/100000
More input is definitely needed
It's fine that we need to get people to update, it's a sunk cost, I'll help with that but it may not be as easy as last time
-
The world is watching and we need to get this as balanced as possible.
As long as these assets can be traded fairly at a reasonable cost and precision, its a win win for everyone.
0.7 BTS or 0.07 BTS fees would be OK now but should we consider the future?
-
How much should the division be exactly, 1000th it is right now and priced in CNY or BTS?
If 7400 BTS is 0.01 it should be 0.000001 correct?
-
To clarify this .. the assets should have had a precision of at least the precision of the denominated asset .. e.g. shenzen in cny .. nikkei in yen ...
-
To clarify this .. the assets should have had a precision of at least the precision of the denominated asset .. e.g. shenzen in cny .. nikkei in hkd ...
Nikkei is in Japan, so yen.
Xeroc, how about the size, 0.00001 or ?
-
... btw .. has anyone tried paying the cover fee in BTS? Shouldnt that be possible to?
-
To clarify this .. the assets should have had a precision of at least the precision of the denominated asset .. e.g. shenzen in cny .. nikkei in hkd ...
Nikkei is in Japan, so yen.
Xeroc, how about the size, 0.00001 or ?
Fixed ..
i am not a trader .. and i dont see we can change the precision without a hardfork ..
-
To clarify this .. the assets should have had a precision of at least the precision of the denominated asset .. e.g. shenzen in cny .. nikkei in hkd ...
Nikkei is in Japan, so yen.
Xeroc, how about the size, 0.00001 or ?
Fixed ..
i am not a trader .. and i dont see we can change the precision without a hardfork ..
If you mean we will have to get 51 delegates again, I understand and will help
-
Which is the simplest option to get everyone trading?
They both have the same complexity because you have to get all the delegates to update their scripts again either way. Here are some pros/cons:
new MPAs
Cons:
* Cost of registration for new MPA names is 5000 BTS / name
* Redundency - the first set of MPAs will continue to exist, with the better names, since the new ones would need to be unique
Pros:
* Can keep the CNY 1:1 pricing
price in BTS
Cons:
* Prices will be less familiar to the chinese traders if a /CNY market becomes available
Pros:
* Cheap to do
* Purity of pricing in BTS, just like the other MPAs
Scale existing CNY pricing down by 1000 (or some other number)
Cons:
* Prices will be unfamiliar to the chinese traders
* Feels dirty
Pros:
* Cheap to do
We're a little bit stuck between a rock and a hard place here...
That's a pretty accurate overview of what our options are, as far as I can tell. None feels perfect, but this should be solved in BitShares 2.0 anyway and in the meantime, I would also slightly prefer the 2nd option, same as Monsterer, it seems the cleanest and has another advantage if we do it: price value shown on the screen will be same in BitShares 0.9.x (as priced in BTS) and in BitShares 2.0 (as it will be priced in the native currency, but the main market will also be ASSET/NATIVE_CUR instead of ASSET/BTS, so the displayed value ends up being the same).
If we have a consensus on the way forward, then I will implement it as soon as possible, but we should wait for all scripts to be updated (xeroc, alt) in the same way before telling the delegates to upgrade, so as to try not to have a broken feed (some delegates publishing in BTS, some publishing in CNY, JPY, ...)
-
Transaction Fee to Cover Short Position is also 0.01 BitNASDAQC - currently 7,400.36 BTS
I haven't thought this through :(
Bitshares is a damn profitable DAC :P
Sent from my ALCATEL ONE TOUCH 997D
-
A little too profitable :o
with option 2
price in BTS
Cons:
* Prices will be less familiar to the chinese traders if a /CNY market becomes available
Pros:
* Cheap to do
* Purity of pricing in BTS, just like the other MPAs
what will the fees cost?
0.01 NASDAQC = ?
0.01 HANGSENG = ?
0.01 NIKKEI = ?
0.01 SHENZHEN = ?
0.01 SHANGHAI = ?
-
what will the fees cost?
0.01 NASDAQC = ?
0.01 HANGSENG = ?
0.01 NIKKEI = ?
0.01 SHENZHEN = ?
0.01 SHANGHAI = ?
With BTS pricing:
0.01 NASDAQC = 50 BTS
0.01 HANGSENG = 266 BTS
0.01 NIKKEI = 204 BTS
0.01 SHENZHEN = 29 BTS
SHANGHAI gone from yahoo ??
So, these are perhaps a little high still :|
-
what will the fees cost?
0.01 NASDAQC = ?
0.01 HANGSENG = ?
0.01 NIKKEI = ?
0.01 SHENZHEN = ?
0.01 SHANGHAI = ?
With BTS pricing:
0.01 NASDAQC = 50 BTS
0.01 HANGSENG = 266 BTS
0.01 NIKKEI = 204 BTS
0.01 SHENZHEN = 29 BTS
SHANGHAI gone from yahoo ??
So, these are perhaps a little high still :|
High but trade-able.
So for the record, I'm for Option 2, 3, 1 (in that order) until Bitshares 2.0 kicks in
-
what will the fees cost?
0.01 NASDAQC = ?
0.01 HANGSENG = ?
0.01 NIKKEI = ?
0.01 SHENZHEN = ?
0.01 SHANGHAI = ?
With BTS pricing:
0.01 NASDAQC = 50 BTS
0.01 HANGSENG = 266 BTS
0.01 NIKKEI = 204 BTS
0.01 SHENZHEN = 29 BTS
SHANGHAI gone from yahoo ??
So, these are perhaps a little high still :|
High but trade-able.
So for the record, I'm for Option 2, 3, 1 (in that order) until Bitshares 2.0 kicks in
Ok! Yeah, I vote for 2 (BTS pricing), then we can have the minimum quantity of the assets adjusted in the next hard fork, be that bitshares 1, or 2 :)
-
SHANGHAI gone from yahoo ??
SHANGHAI has ticker "000001.SS" on yahoo (a bit tricky to find, but it's there). It is however not available through their API (bug?), so I now scrape the yahoo page instead of querying the API directly in order to get this feed.
So if no-one is against it and speaks up in the coming days, I will implement solution 2 in my bts_tools. Then, when Xeroc and Alt have done so also, we need to get the delegates to upgrade again.
And I have one last (small) concern/question: let's suppose we get a hardfork that fixes the asset precision before BitShares 2.0 gets released. What will we do then:
- leave it as is
- revert to the original pricing?
Although probably we only need to start thinking about it if we get this hardfork (not sure it's a high-priority for core devs at the moment, understandably so)
-
And I have one last (small) concern/question: let's suppose we get a hardfork that fixes the asset precision before BitShares 2.0 gets released. What will we do then:
- leave it as is
- revert to the original pricing?
Although probably we only need to start thinking about it if we get this hardfork (not sure it's a high-priority for core devs at the moment, understandably so)
I say leave it - otherwise any existing orders on the book would be put in danger.
-
Also it would be unfair to those that are long .. or short depending the direction you correct the feed to
-
I released version 0.2.9 of my tools which now publish the prices for those indices in BTS instead of their native currencies. I would suggest to wait until the other scripts are updated and then tell all the delegates to upgrade. Let's get those markets open!
-
Good to see these assets back on track :)
-
I released version 0.2.9 of my tools which now publish the prices for those indices in BTS instead of their native currencies. I would suggest to wait until the other scripts are updated and then tell all the delegates to upgrade. Let's get those markets open!
What are the transaction fees now?
-
What are the transaction fees now?
If I understand correctly, once everyone switches to prices in BTS, then the fees will be what Monsterer mentioned here:
With BTS pricing:
0.01 NASDAQC = 50 BTS
0.01 HANGSENG = 266 BTS
0.01 NIKKEI = 204 BTS
0.01 SHENZHEN = 29 BTS
SHANGHAI gone from yahoo ??
So, these are perhaps a little high still :|
and 0.01 SHANGHAI would be 45 BTS
-
So has the script been updated and I can start contacting delegates?
-
What will be the fees when bitshares is at $1 each?
-
What will be the fees when bitshares is at $1 each?
I hope to be on 2.0 with a revised precision for these assets before BTS is $1 ;)
-
So has the script been updated and I can start contacting delegates?
My script has been updated, so people using the bts_tools can update, but I believe Xeroc and Alt's scripts haven't updated yet (Xeroc's still on holidays if I'm not mistaken), and we would have to wait for them to "reopen" the markets. Otherwise, some feeds are going to be in BTS and some others not, and there would be an abrupt change in the prices when more than half the delegates publishing feeds will have switched.
-
What will be the fees when bitshares is at $1 each?
with this precision, still 0.01 of the asset, so:
0.01 NASDAQC = 50 BTS
0.01 HANGSENG = 266 BTS
0.01 NIKKEI = 204 BTS
0.01 SHENZHEN = 29 BTS
0.01 SHANGHAI = 45 BTS
but with 1 BTS = 1$, so you can do the math: quite expensive! ;D
So:
I hope to be on 2.0 with a revised precision for these assets before BTS is $1 ;)
-
I do not know it makes sense to proactively do SOMETHING right now ... I would wait for bts2 .. let the markets do what they do and vote for an changing hardfork when we get the chance (right at bts2 launch)
-
What will be the fees when bitshares is at $1 each?
with this precision, still 0.01 of the asset, so:
0.01 NASDAQC = 50 BTS
0.01 HANGSENG = 266 BTS
0.01 NIKKEI = 204 BTS
0.01 SHENZHEN = 29 BTS
0.01 SHANGHAI = 45 BTS
but with 1 BTS = 1$, so you can do the math: quite expensive! ;D
So
I hope to be on 2.0 with a revised precision for these assets before BTS is $1 ;)
Can we go down to 0.001 precision?
Also Xerox your saying we should wait or release this now to have the first movers advantage?
-
what will the fees cost?
0.01 NASDAQC = ?
0.01 HANGSENG = ?
0.01 NIKKEI = ?
0.01 SHENZHEN = ?
0.01 SHANGHAI = ?
With BTS pricing:
0.01 NASDAQC = 50 BTS
0.01 HANGSENG = 266 BTS
0.01 NIKKEI = 204 BTS
0.01 SHENZHEN = 29 BTS
SHANGHAI gone from yahoo ??
So, these are perhaps a little high still :|
High but trade-able.
So for the record, I'm for Option 2, 3, 1 (in that order) until Bitshares 2.0 kicks in
Ok! Yeah, I vote for 2 (BTS pricing), then we can have the minimum quantity of the assets adjusted in the next hard fork, be that bitshares 1, or 2 :)
Why are we still waiting? Delegates update your scripts!
-
I currently cant update my script .. mobile internet connection only .. no notebook
-
Also Xerox your saying we should wait or release this now to have the first movers advantage?
I say go for it! There's no time like the present.
We just need all the feed authors to post updated versions, then we can get the delegates to update.
-
I currently cant update my script .. mobile internet connection only .. no notebook
To clarify this.
I am happy to wait until Xeroc enjoys the rest of his holidays and then gets the script updated on his return.
I do not want to wait until 2.0 to get these markets trading.
-
Here you go:
https://github.com/xeroc/bitshares-pytools/commit/b6fc70ffb801a7e2869b7ee4b155c27129c30fa8#diff-27bb350ac3c5ac68778a08476c884d8eR379
all indices will be published denominated in BTS
-
Cool
Thanks xeroc +5%
-
My feeds have been updated.
Lets get all delegates on board and start trading these markets now while Greece sends them into a spin :)
-
My delegate feeds (spartako,spartako1,spartako2) are updated with xeroc script.
-
BUMP
Sent from my iPhone using Tapatalk
-
My delegate feeds (spartako,spartako1,spartako2) are updated with xeroc script.
Would you please update your script again .. I skrew up big time with the last commit ..
https://github.com/xeroc/bitshares-pytools/commit/58e3dbb8fb1ca8c98eb553da1b1b582326b12e8d#diff-27bb350ac3c5ac68778a08476c884d8eR225
I noticed today that three different prices exist on the blockchain .. namely:
- the old price
- the new price
- 1/the new price
the latter was my mistake (a dumb one)
fixed it in a new commit ..
Also:
Because the price feed is derived from the MEDIAN of all feeds and we just "changed" the rules, we should first make the market stop entirely instead of having highly inconsistent prices that fuck up the MEDIAN!
Hence, I do not publish the index prices untill at least 51 delegate are willing to publish the NEW price!
-
My delegate feeds (spartako,spartako1,spartako2) are updated with xeroc script.
Would you please update your script again .. I skrew up big time with the last commit ..
https://github.com/xeroc/bitshares-pytools/commit/58e3dbb8fb1ca8c98eb553da1b1b582326b12e8d#diff-27bb350ac3c5ac68778a08476c884d8eR225
I noticed today that three different prices exist on the blockchain .. namely:
- the old price
- the new price
- 1/the new price
the letter was my mistake (a dumb one)
fixed it in a new commit ..
Also:
Because the price feed is derived from the MEDIAN of all feeds and we just "changed" the rules, we should first make the market stop entirely instead of having highly inconsistent prices that fuck up the MEDIAN!
Hence, I do not publish the index prices untill at least 51 delegate are willing to publish the NEW price!
Thanks xeroc, I updated the script
-
updated
-
Thanks, script updated.
-
Can someone clarify changes in the price feed? Paging @xeroc and @alt
-
Can someone clarify changes in the price feed? Paging @xeroc and @alt
my last change fixed a bug that reported the price reversed (1/x) ..
the price for on NASDAQ should be 1 / (reported price of the index) ...
hence .. with about 5k BTS you can buy 1 NASDAQ
-
I have update my scripts
because the feed price change more than 50%,
it will refused to publish the new feed, until the market is disable, or the feed is change to the new version
-
Maybe a silly question.
But how would we handle a situation where an index is no longer used/discontinued/another group of assets looked at instead etc.
Im more thinking along the lines of having unit-trust market pegged assets.
A unit trust may stick around for say 20 years, we could therefore have an asset that tracks the value of a single unit. But what happens when its shut down.
-
Because the price feed is derived from the MEDIAN of all feeds and we just "changed" the rules, we should first make the market stop entirely instead of having highly inconsistent prices that fuck up the MEDIAN!
Hence, I do not publish the index prices untill at least 51 delegate are willing to publish the NEW price!
I agree that it would be better to have everyone upgrade in a synchronized way, but that's probably going to be really hard to achieve. Given that the combined depth of all those markets currently is 116 BTS for bid, and 0 BTS for ask, I'd say we can start upgrading the delegate's script (let's say that the markets are unofficially closed, even though it's not technically true). Once, say, 80% of the delegates producing feeds have upgraded, then we should be able to "re-open" the markets by making a public announcement that they are working correctly and that traders can start placing their orders. What do you think?
-
This thread is a good example of how difficult it is to game the price feed!
Are these assets trade-able now?
-
Are these assets trade-able now?
Not yet, currently the distribution is the following:
old price feed (38 delegates):
calabiyau
emski
riverhead-del-server-1
angel.bitdelegate
emski.bitdelegate
delegate.xeldal
delegate2.xeldal
btsx.chinesecommunity
delegate.liondani
www.minebitshares-com
www2.minebitshares-com
google.helloworld
microsoft.helloworld
x.ebit
rose.ebit
delegate.btsnow
immortal.bitdelegate
delegate-clayop
dev.bitsharesblocks
backbone.riverhead
marketing.methodx
stan.delegate.xeldal
bm.payroll.riverhead
del0.cass
argentina-marketing.matt608
jcalfee1-developer-team.helper.liondani
delegate-dev1.btsnow
delegate-dev2.btsnow
delegate-dev4.btsnow
delegate-dev3.btsnow
market.cn.group101
delegate.rgcrypto
fuzzy.beyondbitcoin
fund.bitsharesbreakout
minebitshares-reloaded
sollywood.sollars-com
delegate.dposhub-org
chronos.payroll.lafona
new price feed (25 delegates):
testz
spartako
spartako2
spartako1
dele-puppy
delegate-alt
delegate-baozi
delegate-watchman
wackou-delegate
maqifrnswa
delegate.baozi
delegate.bitsuperlab
delegate1.maqifrnswa
delegate.ihashfury
dev-metaexchange.monsterer
btstools.digitalgaia
valzav.payroll.testz
www.bts-hk
delegate.verbaltech
minebts1.bunkermining-com
minebts3.bunkermining-com
minebts4.bunkermining-com
minebts5.bunkermining-com
minebts6.bunkermining-com
minebts2.bunkermining-com
We need at least half of the delegates to switch in order to get the new price feed, but I would actually wait that 75-80% have switched, in order to have a more stable feed.
-
+5%
Come on ! Delegates.
-
I have update my scripts
because the feed price change more than 50%,
it will refused to publish the new feed, until the market is disable, or the feed is change to the new version
if you want publish imeediately, you need to edit config file ~/.python-bts/delegate_taks.json
change "change_max" to a big number, like 50000
when the feed price is correct, you'd better change that back for safety reason.