BitShares Forum
Main => Stakeholder Proposals => Topic started by: roelandp on April 19, 2017, 10:01:22 am
-
Dear Bitshares community! Some of you have already voted my witness roelandp, thank you! In this topic I will introduce myself, my witness server portfolio and what I intend to add to the Bitshares community.
Who am I?
My name is RoelandP from Amsterdam. I am a developer of (mostly) mobile apps (https://shoudio.com) and in the crypto world I have been very active on Steemit by launching several Steem related apps as well as an app overview site called SteemTools (http://SteemTools.com). Since about 2003 I make a living by making sites & apps and some photoshopping / designing for my parents' pancake restaurant (http://pannekoekenmolen.nl) on the side :)
I have studied Hotelschool in The Hague and made my first homepage in 1996 after which I got hooked on coding and learned it through the internets. Next to coding I love to kitesurf and I am since 1 year a dad of our son, who is slowly learning to sleep during the nights and together with my gf we run a small Poop Emoji webshop (http://littlepoopfactory.com).
After my study I have worked at several festivals and organised some hackathons like Music Hackday Amsterdam. Last year I organised SteemFest in Amsterdam, which was a blast!
I've been running as an active witness for Steem & Golos for a while now and have been supporting the Bitshares network since late September last year with a dedicated server public seednode on seed.roelandp.nl:1776 (listed on @wackou's seednode statuspage (http://status.bitsharesnodes.com) and hardcoded in the bitshares sourcecode (https://github.com/bitshares/bitshares-core/pull/19/commits/4251d40ab82cfe519d2a3c562037d3f6c9403649#diff-96eeb53aa89c9bb1313e838c970913f0))
My current server portfolio setup for Bitshares is as follows:
Public Seed:
- Type: Dedicated
- Processor: Intel Xeon D-1521
- Cores: 4
- Ram: 32 GB DDR4
- HDD: 2 x 2 TB
- Connection: 1 Gbit/s
- Location: Canada
Witness signing server:
- Type: Dedicated
- Processor: Intel i7-6700
- Cores: 4
- Ram: 64 GB DDR4
- HDD: 2 x 250 GB SSD
- Connection: 1 Gbit/s
- Location: Germany
Backup witness signing server:
- Type: Dedicated
- Processor: Intel Xeon D-1531
- Cores: 6
- Ram: 32 GB DDR4
- HDD: 2 x 250 GB SSD
- Connection: 300 Mbit/s
- Location: France
Backup Seed:
- Type: Dedicated
- Processor: Intel i7-6700
- Cores: 4
- Ram: 64 GB DDR4
- HDD: 2 x 250 GB SSD
- Connection: 1 Gbit/s
- Location: Germany
Public Websocket node - btsws.roelandp.nl/ws (http://"https://btsws.roelandp.nl/ws"):
- Type: Dedicated
- Processor: Intel i7-6700
- Cores: 4
- Ram: 64 GB DDR4
- HDD: 2 x 500 GB SSD
- Connection: 1 Gbit/s
- Location: Finland
Test VPS's readily available:
- Location: Netherlands (Amsterdam, Transip.nl)
- Location: USA (Chicago, Rackspace.com)
- Location: UK (London, Atlantic.net)
Additional Backup VPS's (if needed) can be setup through my Google Cloud and Amazon Webservices accounts on which I have run the graphene software before.
I have been experimenting with the pricefeed software from @xeroc and together with @iHashFury I setup the Altcap.XDR which we are both publishing every other half an hour. I am ready to fire the "regular" pricefeed updates.
What value can I add to the Bitshares community?
- Thrustworthy witness with reliable infrastructure. I have missed 5 blocks on Steem and 1 on Golos in half a year of active signing.
- Fresh blood!
- Coding experience: PHP, javascript, python, mysql. Helped out @fav with a referral code script (https://bitsharestalk.org/index.php?topic=23995.msg304611#msg304611") and @iHashFury with code reviewing the Altcap.XDR script. I've made available on my Github a Steem Witness Monitoring script (http://"https://github.com/roelandp/witnesshealthcheck") and a Golos Pricefeed script (https://github.com/roelandp/golospricefeed)
- Creativity, see a sample of my Steem Apps by visiting SteemTools.com (http://steemtools.com) and search for 'roelandp'.
- Event experience: As said, I organised SteemFest in Amsterdam last year with the support of many and about 200 attendees, which was a blast! Would love to set something like this up for Bitshares (or a combo) one (not to far in the future) day!
- Promote Bitshares: (don't we all :D). Past 6 months I was invited and I have presented Steem on 2 (non crypto) events in presentation slots and panel discussion. For future talks I will incorporate more time for Bitshares when invited. Additionally I am working on a UIA which I reveal soon and think it can trigger some nice promotion for Bitshares!
Can I have your vote? Vote roelandp
Ask me questions here or ping me directly via:
- @roelandp on Telegram / Mumble
- email: roelandp.steem att gmail d.o.t com
- site: http://roelandp.nl
Proof of Face:
- Keybase.io @roelandp (https://keybase.io/roelandp)
- Linkedin @roelandp (https://linkedin.com/in/roelandp)
To Jupiter's Moon! [/list][/list]
-
any apps for bitshares planned?
great proposal btw, I'll vote asap.
-
any apps for bitshares planned?
great proposal btw, I'll vote asap.
Much appreciated! Atm. no bitshares apps planned, but if you have any suggestions... Let me know! I do am working on a fun UIA which I can reveal more about soon.
-
Great introduction, roelandp and welcome to the BitShares community.
It's a perfect timing to get yourself acquainted with the tech.
Would you be open to help organize a BitShares-dedicated event in Munich sometime?
-
Great introduction, roelandp and welcome to the BitShares community.
It's a perfect timing to get yourself acquainted with the tech.
Would you be open to help organize a BitShares-dedicated event in Munich sometime?
Definitely!
Sent from my iPhone using Tapatalk
-
Great introduction, roelandp and welcome to the BitShares community.
It's a perfect timing to get yourself acquainted with the tech.
Would you be open to help organize a BitShares-dedicated event in Munich sometime?
That would be awesome @roelandp did a fantastic job with steemfest, Munich is the perfect location too.
roelandp witness already has my vote.
-
indeed, great to see you here roelandp! you have my vote also (through xeroc). Very much looking forward to your bts endeavours :)
-
- Coding experience: PHP, javascript, python, mysql. Helped out @fav with a referral code script (https://bitsharestalk.org/index.php?topic=23995.msg304611#msg304611") and @iHashFury with code reviewing the Altcap.XDR script. I've made available on my Github a Steem Witness Monitoring script (http://"https://github.com/roelandp/witnesshealthcheck") and a Golos Pricefeed script (https://github.com/roelandp/golospricefeed)
Great proposal!
Your price feed script has only:
and I see you are working on Poloniex. Do you plan to add other feeds to cover MPAs?
[/list]
-
@sahkan I guess this is for Golos (Steem fork) internal exchange.
-
- Coding experience: PHP, javascript, python, mysql. Helped out @fav with a referral code script (https://bitsharestalk.org/index.php?topic=23995.msg304611#msg304611") and @iHashFury with code reviewing the Altcap.XDR script. I've made available on my Github a Steem Witness Monitoring script (http://"https://github.com/roelandp/witnesshealthcheck") and a Golos Pricefeed script (https://github.com/roelandp/golospricefeed)
Great proposal!
Your price feed script has only:
and I see you are working on Poloniex. Do you plan to add other feeds to cover MPAs?
[/list]
Hi @sahkan thank you for notifiying. As I mentioned that was a sample of code I supplied to other graphene communities. In this case Golos. Being a Golos witness means supplying a dedicated Golos feed to the Golos blockchain. The Golos coin was only listed on those 4 exchanges. (Now only on 3 for the moment). Hence that specific pricescript only has those exchanges incorporated.
Re: your question:
I currently plan to use @xeroc 's pricefeed script which I have tested but can not publish the feeds which are only for active witnesses. If you check Bitshares overview (https://bitshares.openledger.info/account/roelandp/overview) you will notice that I currently publish ALTCAP.XDR. This is a script I codereviewed from @iHashFury and intend to have that 'manual' script for more MPA's yes.
-
@sahkan I guess this is for Golos (Steem fork) internal exchange.
Yes, thanks for clarifying @nmywn! +5%
-
- Coding experience: PHP, javascript, python, mysql. Helped out @fav with a referral code script (https://bitsharestalk.org/index.php?topic=23995.msg304611#msg304611") and @iHashFury with code reviewing the Altcap.XDR script. I've made available on my Github a Steem Witness Monitoring script (http://"https://github.com/roelandp/witnesshealthcheck") and a Golos Pricefeed script (https://github.com/roelandp/golospricefeed)
Great proposal!
Your price feed script has only:
and I see you are working on Poloniex. Do you plan to add other feeds to cover MPAs?
[/list]
Hi @sahkan thank you for notifiying. As I mentioned that was a sample of code I supplied to other graphene communities. In this case Golos. Being a Golos witness means supplying a dedicated Golos feed to the Golos blockchain. The Golos coin was only listed on those 4 exchanges. (Now only on 3 for the moment). Hence that specific pricescript only has those exchanges incorporated.
Re: your question:
I currently plan to use @xeroc 's pricefeed script which I have tested but can not publish the feeds which are only for active witnesses. If you check Bitshares overview (https://bitshares.openledger.info/account/roelandp/overview) you will notice that I currently publish ALTCAP.XDR. This is a script I codereviewed from @iHashFury and intend to have that 'manual' script for more MPA's yes.
wait a minute, we got a XDR up and running? where's the announcement? who else is feeding the price?
I'm a huge fan of XDR
-
wait a minute, we got a XDR up and running? where's the announcement? who else is feeding the price?
I'm a huge fan of XDR
@iHashFury is also feeding but I hope I have not spilled beans on anything now?
-
- Coding experience: PHP, javascript, python, mysql. Helped out @fav with a referral code script (https://bitsharestalk.org/index.php?topic=23995.msg304611#msg304611") and @iHashFury with code reviewing the Altcap.XDR script. I've made available on my Github a Steem Witness Monitoring script (http://"https://github.com/roelandp/witnesshealthcheck") and a Golos Pricefeed script (https://github.com/roelandp/golospricefeed)
Great proposal!
Your price feed script has only:
and I see you are working on Poloniex. Do you plan to add other feeds to cover MPAs?
[/list]
Hi @sahkan thank you for notifiying. As I mentioned that was a sample of code I supplied to other graphene communities. In this case Golos. Being a Golos witness means supplying a dedicated Golos feed to the Golos blockchain. The Golos coin was only listed on those 4 exchanges. (Now only on 3 for the moment). Hence that specific pricescript only has those exchanges incorporated.
Re: your question:
I currently plan to use @xeroc 's pricefeed script which I have tested but can not publish the feeds which are only for active witnesses. If you check Bitshares overview (https://bitshares.openledger.info/account/roelandp/overview) you will notice that I currently publish ALTCAP.XDR. This is a script I codereviewed from @iHashFury and intend to have that 'manual' script for more MPA's yes.
I don't want to saturate your proposal here, but I am trying to get a grip on this price feeding so we can get some governance and guidance that all witnesses are willing to follow. A list of required price feeds should be one of them. Please provide some feedback at https://bitsharestalk.org/index.php/topic,24006.0.html Thanks!
-
I don't want to saturate your proposal here
LOL :) but you are :D I was already monitoring your talks but tonight busy with having a cronjob running for the pricefeed and debugging some parts of BTC38 API in xeroc's script, which seems to fail on some pairs.
-
Welcome rolandp, glad to have you among the dedicated graphene witnesses! You have my vote (thru xeroc proxy) already.
Anxious to see your contribution to the security of the network.
Your hardware "portfolio" is excellent, top notch. Hopefully you can help us establish some witness standards to strengthen the security and robustness of BitShares.
-
Your hardware "portfolio" is excellent, top notch. Hopefully you can help us establish some witness standards to strengthen the security and robustness of BitShares.
Thanks Thom for your proxy vote :)
-
Your expertise is welcomed and needed. I would love to see a Blockfolio style app or site dedicated to Bitshares ecosystem.
Sent from my SM-N920T using Tapatalk
-
Your expertise is welcomed and needed. I would love to see a Blockfolio style app or site dedicated to Bitshares ecosystem.
Sent from my SM-N920T using Tapatalk
or for free marketing: help blockfolio to add bitshares dex api
-
@fav, i noticed that Blockfolio has the following pairs from Bitshares: BTS / BTC, BTS / CNY, PTS/BTC. You want them to have the Dex added as one of the exchanges to make them watch for?
@Pheonike would this be an app were you can glance your bitshares portfolio iaw your account_balances? Sounds like a fun app / site to make. I can see when I can put some time in this. It is totally possible with the cli_wallet / websocket.
-
Exactly, I want them to add bts as exchange, so that we can track our assets
-
Bunkerchainlabs-com proxy is supporting this witness.
-
Bunkerchainlabs-com proxy is supporting this witness.
Thanks a great bunch!
-
@fav, i noticed that Blockfolio has the following pairs from Bitshares: BTS / BTC, BTS / CNY, PTS/BTC. You want them to have the Dex added as one of the exchanges to make them watch for?
@Pheonike would this be an app were you can glance your bitshares portfolio iaw your account_balances? Sounds like a fun app / site to make. I can see when I can put some time in this. It is totally possible with the cli_wallet / websocket.
Yeah, Just be able to track account balances. Just add the account name and track profit/loss.
-
Yeah, Just be able to track account balances. Just add the account name and track profit/loss.
Cool, experimented a bit with @svk 's libs and got some rudimentary working... WIP very much: I used your balance :)
Updated @Pheonike ! Let me know if this is what you are looking for? Do you need additional data?
(http://i.imgur.com/2XBK3L0.png)
-
voted.
now there are only 19 witnesses, if roelandp is voted in, another will be voted out.
how about to increase the number of witnesses to let more effective witnesses in? @xeroc is it possible for you to vote more witnesses?
-
Curious, WHY are there only 19 witnesses, did the committee vote to change that from 21 to 19?
From 24 to 21 to 19. Who or what is driving these changes?
We do have 2 new witnesses (rolandp and sahkan) who I believe will be great additions. I am curious tho on the drop to 19.
-
Curious, WHY are there only 19 witnesses, did the committee vote to change that from 21 to 19?
From 24 to 21 to 19. Who or what is driving these changes?
The number of witness slots is the weighted average of the number of witnesses voted for by a given voter (proxy). Proxies voting for fewer witnesses will reduce the witness slots, which is what recently happened, resulting in two slots being eliminated. The number of witness slots is always an odd number and may not be less than 11. The committee has no impact on witness slots.
-
Curious, WHY are there only 19 witnesses, did the committee vote to change that from 21 to 19?
From 24 to 21 to 19. Who or what is driving these changes?
The number of witness slots is the weighted average of the number of witnesses voted for by a given voter (proxy). Proxies voting for fewer witnesses will reduce the witness slots, which is what recently happened, resulting in two slots being eliminated. The number of witness slots is always an odd number and may not be less than 11. The committee has no impact on witness slots.
Thanks for that fox, I had no idea. Somewhere along the way I got it in my head it was just another committee parameter.
So if I understood you correctly the count is directly related to how many witnesses each vote proxy votes for. What do you mean by "weighted" average? And how do votes from individual accounts factor in?
In essence reduction of the number of witnesses gives the remaining witnesses more opportunities to produce a block and hence pay increases.
-
@Thom this is what I found about it:
http://docs.bitshares.eu/bitshares/dpos.html#how-many-witnesses-are-securing-the-network (http://docs.bitshares.eu/bitshares/dpos.html#how-many-witnesses-are-securing-the-network)
HOW MANY WITNESSES ARE SECURING THE NETWORK
This is totally in the hands of the shareholders. If the majority votes for 50 witnesses, then 50 witnesses will be used. If the shareholders only vote for 20, so be it. The minimum possible witness count is 11.
I think here is the counter code: db_maint.cpp#L159 (https://github.com/bitshares/bitshares-core/blob/master/libraries/chain/db_maint.cpp#L159)
-
+5% ;)
-
Made a witness monitor script to check the 3 core witness tasks on regular intervals, see: https://bitsharestalk.org/index.php/topic,24042.0.html
-
I released a new Bitshares tool today: Public Bitshares Witness Log: Check it out here: https://bitsharestalk.org/index.php/topic,24069.msg305401.html#msg305401
It displays current pricefeeds for witnesses and missed blocks and updates 3 times per hour. Direct link: http://roelandp.nl/bitshareswitnesslog
-
+5%
Glad to see the witness team injected fresh blood.
In-depth study of BitShares 2.0, I believe you will fall in love with her, to play your talent, to expand the ecosystem of BitShares.
I'm a proxy, you have my vote!
Voting status will be updated in 16:00 ( UTC+8 ).
-
+5%
Glad to see the witness team injected fresh blood.
In-depth study of BitShares 2.0, I believe you will fall in love with her, to play your talent, to expand the ecosystem of BitShares.
I'm a proxy, you have my vote!
Voting status will be updated in 16:00 ( UTC+8 ).
EPIC thx Yao! fyi, i was already supporting Bitshares with a public seednode for about half a year, but now wanted to be more serious. Thanks for your vote!
-
I noticed that, thx for your job. +5%
+5%
Glad to see the witness team injected fresh blood.
In-depth study of BitShares 2.0, I believe you will fall in love with her, to play your talent, to expand the ecosystem of BitShares.
I'm a proxy, you have my vote!
Voting status will be updated in 16:00 ( UTC+8 ).
EPIC thx Yao! fyi, i was already supporting Bitshares with a public seednode for about half a year, but now wanted to be more serious. Thanks for your vote!
-
Made a witness monitor script to check the 3 core witness tasks on regular intervals, see: https://bitsharestalk.org/index.php/topic,24042.0.html
Would you be willing to make this open source?
-
Made a witness monitor script to check the 3 core witness tasks on regular intervals, see: https://bitsharestalk.org/index.php/topic,24042.0.html
Would you be willing to make this open source?
It was already as announced in the post you link to in your quote :P
https://github.com/roelandp/Bitshares-Witness-Monitor
-
Made a witness monitor script to check the 3 core witness tasks on regular intervals, see: https://bitsharestalk.org/index.php/topic,24042.0.html
Would you be willing to make this open source?
It was already as announced in the post you link to in your quote :P
https://github.com/roelandp/Bitshares-Witness-Monitor
You are such a great witness! No wonder I voted for you :D
I was thinking that maybe over time we can morph it into a BTS block explorer....
-
You are such a great witness! No wonder I voted for you :D
I was thinking that maybe over time we can morph it into a BTS block explorer....
:D thank you! but https://cryptofresh.com ?
-
You are such a great witness! No wonder I voted for you :D
I was thinking that maybe over time we can morph it into a BTS block explorer....
:D thank you! but https://cryptofresh.com ?
It's not open source. I also meant this: http://roelandp.nl/bitshareswitnesslog/ for an open source
-
Hi Sakhan, that page is just a viewer for the datafile which is being created and stored here: http://s3.amazonaws.com/roelandp-nl/witnesslog.json every 15 minutes. The source for the logger is a mysql database in which I store the assets and basically the results from the other script I wrote, but then for all witnesses. IMHO a block explorer would require a different set of logging also logging different calls and update on each block. The code for the Bitshares Witness Log logger into mysql is not really worth publishing as I am still learning python :P
-
Made a little witness server report tool, to keep an eye on your disk-space, ram usage & cpu usage and get a report as often as you like (via cronjob), see ann at https://bitsharestalk.org/index.php/topic,24105.msg305715.html
-
RE: http://roelandp.nl/bitshareswitnesslog/ (Great site BTW):
Would it be possible to indicate historical reliability of price feeds? Perhaps the avg variance and the avg time between price feed updates over x days?
Thanks :)
-
RE: http://roelandp.nl/bitshareswitnesslog/ (Great site BTW):
Would it be possible to indicate historical reliability of price feeds? Perhaps the avg variance and the avg time between price feed updates over x days?
Thanks :)
@lafona is working on that here: https://lafona.net/witness-stats/
-
RE: http://roelandp.nl/bitshareswitnesslog/ (Great site BTW):
Would it be possible to indicate historical reliability of price feeds? Perhaps the avg variance and the avg time between price feed updates over x days?
Thanks :)
I could also start calculating variance difference for every publication. However variance is a subjective thing: A witness can post a high variance pricefeed because the markets are suddenly moving into a new direction and others have not yet responded with new price feeds, so the median is still reflecting the 'old' market and will gradually change when new pricefeeds come available. Average variance over a rolling time will therefore be all in the same range I think.
Yes I can add the 'publishing frequency' as I log all unique pricefeed entries. Feed frequency could be interesting, but can be a subjective indicator as well, misleading. One witness cannot update pricefeeds as long as markets are not volatile and stable without many changes... Pricefeeds are based on feeds published with 24h window, and if markets are not changing, there is no need to publish new feeds and therefore this influences the average pricefeed publication frequency number. So there are not really conclusions to draw from...
Thanks for your feedback @Customminer and please take a minute to check out the recent GUI changes of the tool.
-
@svk created a witness explorer in BitShares 0.X and it included feed frequency as one of the important metrics. I bet all feeds are produced on a cron schedule or some regular timer so frequency is an important metric for feeds, especially in volatile markets.
You are doing a marvelous job BTW, refining your tool, interacting with users to gain important feedback etc. Great customer interaction!
-
Organising SteemFest (https://steemfest.com) again. This year it will be in Lisbon, 1/2/3/4/5 November. Many BTS'ers are coming! And now... Adding a Blockchain Hackathon in the mix!
Asking for Bitshares stakeholders to support a (small) worker for sponsorship for promoting Bitshares as a Focus Chain on the hackathon. Please, see the announcement:
https://bitsharestalk.org/index.php/topic,24937.0.html (https://bitsharestalk.org/index.php/topic,24937.0.html)
-
Updates!
- SteemFest was great again and with help of the worker we could organise the hackathon as well! Thanks, community, for voting in the worker. Please see https://bitsharestalk.org/index.php/topic,24937.0.html for the full report.
- Just before HF 18 @alt has unfortunately decided to stop btsbots.com and therefore urged witnesses to stop using the btsprice-tool as it used an api for a formatted version of the dex' orderbooks he ran off the btsbots.com domain/node. Personally I was very disappointed as I am a huge fan of the precision and durability (and lightweightness) of his script/tool. Therefore I setup a stack of JSON API-endpoints (basically static 5 min cached files) mimicking the expected results of the orderbook api which @alt used to have available on BtsBots.com.
- You can find all static api files (cached about 5 mins) here: http://roelandp-nl.s3.amazonaws.com/btsbots-api-result/index.html
- On this script you can see how I compose the API static files with python-bitshares: https://github.com/roelandp/btsprice/blob/master/docs/btsbot-mimick.py
- And finally, these are the changes you must apply to support the new url for picking up the orderbooks: https://github.com/pch957/btsprice/commit/3f87e858fa92e6ddd5094e94e511301a32d85728
Rest assured I hope Alt will some day return to Bitshares! - With HF18 the black swanned assets have now been revived and I've setup a repo sharing some of the custom pricefeed scripts I use to feed a couple of smartcoins. You can check em out here: https://github.com/roelandp/bts-misc-pricefeeds
Thank you for your trust.
-
Updates!
- SteemFest was great again and with help of the worker we could organise the hackathon as well! Thanks, community, for voting in the worker. Please see https://bitsharestalk.org/index.php/topic,24937.0.html for the full report.
- Just before HF 18 @alt has unfortunately decided to stop btsbots.com and therefore urged witnesses to stop using the btsprice-tool as it used an api for a formatted version of the dex' orderbooks he ran off the btsbots.com domain/node. Personally I was very disappointed as I am a huge fan of the precision and durability (and lightweightness) of his script/tool. Therefore I setup a stack of JSON API-endpoints (basically static 5 min cached files) mimicking the expected results of the orderbook api which @alt used to have available on BtsBots.com.
- You can find all static api files (cached about 5 mins) here: http://roelandp-nl.s3.amazonaws.com/btsbots-api-result/index.html
- On this script you can see how I compose the API static files with python-bitshares: https://github.com/roelandp/btsprice/blob/master/docs/btsbot-mimick.py
- And finally, these are the changes you must apply to support the new url for picking up the orderbooks: https://github.com/pch957/btsprice/commit/3f87e858fa92e6ddd5094e94e511301a32d85728
Rest assured I hope Alt will some day return to Bitshares! - With HF18 the black swanned assets have now been revived and I've setup a repo sharing some of the custom pricefeed scripts I use to feed a couple of smartcoins. You can check em out here: https://github.com/roelandp/bts-misc-pricefeeds
Thank you for your trust.
+5%
-
@roelandp : Could you please begin publishing price feeds for the 'Hertz' asset? I would massively appreciate your support.
Hertz (Hz) is a Algorithm Based Asset (ABA) which is pegged against the USD and modified to oscillate using a sine wave, thus we are able to create potential phases of buying and selling pressure.
Important Smartcoin settings:
- Maintenance collateral ratio (MCR): 175%
- Maximum short squeeze ratio (MSSR): 150%
- Max feed lifetime: 1440
- Delay for forced settlements (minutes): 720
- Percent offset of forced settlements: 1%
- Min number of feeds: 7
Properties of Hertz (Hz):
- Amplitude: 14% (NOT 33% nor 50% - It was changed to 14% for the first HERTZ asset).
- Period: 28 days.
- Daily price feed change: 2% per day.
- Max price feed rate: $1.14
- Min price feed rate: $0.86
Price feed scripts:
- Reference scripts & calculator: https://github.com/BTS-CM/scripts (https://github.com/BTS-CM/scripts)
- Wackou's 'BTS_Tools' (Only use once pull request #36 is merged): https://github.com/wackou/bts_tools/pull/36 (https://github.com/wackou/bts_tools/pull/36)
- Xeroc's 'Bitshares-PriceFeed': https://github.com/xeroc/bitshares-pricefeed (https://github.com/xeroc/bitshares-pricefeed)
http://open-explorer.io/#/assets/HERTZ
Many thanks,
CM.
-
Hey @Customminer great, sounds interesting, would love to learn a bit more about your thoughts behind the oscillation. Do you have some more info on the (fixed) formula and where can I learn a bit more about the Hertz asset? ... what day would be 0% etc. etc.
-
Hey @Customminer great, sounds interesting, would love to learn a bit more about your thoughts behind the oscillation. Do you have some more info on the (fixed) formula and where can I learn a bit more about the Hertz asset? ... what day would be 0% etc. etc.
Hey,
Within my repo (https://github.com/BTS-CM/scripts) the following files are worth looking at:
* hertz_calculator.xlsx : A spreadsheet for evaluating the effect of different sine wave variables (amplitude, period, etc).
* hertz-verification.py : Used for verifying that the phase offset lines up appropriately.
* hertz-feed.py : What you'd use if you don't use wackou or xeroc's price feed scripts.
Within wackou's repo, here's my code entries: (Note: The pull request #36 needs implemented, or you can change 1/3 to 0.14 if using this script library)
* https://github.com/wackou/bts_tools/blob/master/bts_tools/feeds.py#L275
* https://github.com/wackou/bts_tools/blob/master/bts_tools/feeds.py#L441
And within xeroc's repo: (Issue #25 addresses the inaccurate amplitude comments)
* https://github.com/xeroc/bitshares-pricefeed/blob/master/bitshares_pricefeed/examples/hertz.yaml
Example python code snippet:
hz_reference_timestamp = pendulum.parse(reference_timestamp).timestamp() # Retrieving the Bitshares2.0 genesis block timestamp
hz_period = pendulum.SECONDS_PER_DAY * period_days
hz_phase = pendulum.SECONDS_PER_DAY * phase_days
hz_waveform = math.sin(((((current_timestamp - (hz_reference_timestamp + hz_phase))/hz_period) % 1) * hz_period) * ((2*math.pi)/hz_period)) # Only change for an alternative HERTZ ABA.
hz_value = reference_asset_value + ((amplitude * reference_asset_value) * hz_waveform)
---
So The idea is that with 14% amplitude, and a period of 28 days the value changes 2% every day. We use a phase offset (date/time) to make Wednesday (mid working week) the most important day for Hertz. On Wednesdays, Hertz price feed should be: $1.00 (start), $1.14 (first week passed), $1.00 (2nd week passed), $0.86 (3rd week), $1.00 (final week -> repeat). Check out the spreadsheet calculator to see the value through the month.
I've got some thoughts regarding how the market could potentially react: https://steemit.com/hertz/@cm-steem/what-is-the-hertz-algorithm-based-asset
Regarding oscillation, I believe that we could create phases of buying and sell pressure (through debt destruction as the price feed decreases & price appreciation as it increases), whether this will be realized and become popular is unknown. To make the first Hertz token stable, I significantly reduced the planned amplitude from 50% to 14%. A high amplitude would require high frequency price feed publishing, by decreasing the amplitude I was able to increase the maximum pricefeed lifetime from 220 to 1440 (more acceptable for publishers, hopefully).
Ideally, if this succeeds, we'll see similar algorithm based assets issued which oscillate using different wave equations (cos instead of sin) as well as different hertz parameters (within reason) and backing asset. The reason I created the spreadsheet calculator was for not just my own research but to spread the idea so that others may consider making similar ABAs.
It'd be interesting to create an opposite hertz token with the same parameters except a 2 week phase offset to produce the exact opposite price feed modification/oscillation.
Do you have any specific questions about Hertz?
-
cool, for now I'll join the experiment!
-
cool, for now I'll join the experiment!
Excellent, thanks for your participation :)
Now to get another 6 witnesses onboard & Hertz will be live!
-
@roelandp: What price feed script are you using? You're quite far out from the intended price feed value.
I've added a public API for looking up a reference Hertz price feed: https://btsapi.grcnode.co.uk/get_hertz_value?api_key=123abc
Thanks
-
https://gist.github.com/roelandp/a676e2915ca9ac999cecab90f698e5c6#file-pf-hertz-py-L61
if we need to go back & forth quicklier, please hook me up on telegram. you can guess my username.
-
Wow, time flies! Almost a year since my original witness announcement.
I've just recently fired up a websocket api node at wss://btsws.roelandp.nl/ws (https://btsws.roelandp.nl)
The past year was great full of highs & lows but my main highs were organising SteemFest in Lisbon (including organising a hackathon for Bitshares and other graphene chains) and most excitement was the shutdown and restart of the BTS chain past july due to an unforeseen error in the BTS software. (fyi: main lows were in family health sphere :( )
I would like to take an opportunity to summarise my contributions for Bitshares platform past year, if people drop by this thread:
- Made various witness tools for server monitoring and automated failover switching when a node starts missing blocks. See my github: https://github.com/roelandp (https://github.com/roelandp)
- Made adjustments for alt's BTS-bot price tool to keep it running after he left the platform including setting up a mimick api for feeding dex-data into the bot: http://roelandp-nl.s3.amazonaws.com/btsbots-api-result/index.html (http://roelandp-nl.s3.amazonaws.com/btsbots-api-result/index.html) - You need my bts-bot fork (see my github (https://github.com/roelandp))
- Setup the oft used pricefeed monitoring tool: https://roelandp.nl/bitshareswitnesslog (https://roelandp.nl/bitshareswitnesslog)
- Several individual pricefeed scripts for smart coins - see my github (https://github.com/roelandp).
- Organised a hackathon for bitshares during Steemfest (https://steemfest.com) last year in Lisbon.
- Was actively participating in relaunching the blockchain during last july's crash.
Thank you for your enduring trust and let's make it another great year for the Dex!
-
(https://i.imgur.com/smhPhoM.gif) (https://goo.gl/forms/uShO5bfp4CnluHsl2)
(https://i.imgur.com/CqsInVl.gif)
Hey hey as you all probably know bitshares.foundation is organising the first BitFest Conference (https://bitfest.in) from Fri, 21 Sep 2018, 12:00 – Sun, 23 Sep 2018, in Amsterdam, my hometown. Looking forward to meeting many of you there... Don't have a ticket yet? Check out https://bitfest.in for details and the shoppe!
Seeing so many BTS'sers flocking to Amsterdam's capital I can't resist to add my share to the program by bringing signature dutch pancakes (family recipe, my brother has a pancake restaurant), on the personally sponsored 'BitFest Farewell Pancakes' event in the Volkshotel on the Sunday 23 September from 10AM - 1PM (aboutish).
Before heading back to home, I invite you for a last moment of togetherness. Close off Bitfest with some breakfast pancakes and a coffee or other drink, courtesy of urs witness. Next to running a reliable block producer, pricefeeds, seed node and rpc node, some add-on apps / scripts for the community I feel every witness should bake pancakes. :P
BitFest Farewell Pancakes
Sunday 23 September - 10 AM - 1 PM
Volkshotel - Petit Canvas (7th Floor)
Address: Wibautstraat 150, 1091 GR Amsterdam
Subway: 51,53,54 - 5 mins from Central Station
- afterwards easy to go to Schiphol by Uber or Train too. (Amstel Station is on 100 meters)
Participation: free for Bitfest Attendees, bring your badge so waiters are not in doubt.
RSVP in advance (for groceries) obligatory - Please signup via: https://goo.gl/forms/uShO5bfp4CnluHsl2
-
there's someways to get smartcoin premium, for bitCNY, you can
1. get the bitCNY deposit/withdraw fee from magicwallet and then calculate out the bitCNY premium.
or
2. from exchange like AEX or ZB get BTS price in CNC or QC, it can be regarded as BTS price in fiat as CNC and
QC are IOU of CNY. with the BTS price in bitCNY, you can calculate out the premium,
new feed price=old feed price*(bitcny/cny+0.02）^3
-
Hey RoelandP, It was great meeting you in person briefly at the Bitfest event.
Would you be interested in publishing price feeds for 3 new Algorithm Based Assets on the BTS DEX? They're called Verthandi, Skuld and Urthr.
https://whaleshares.io/bitshares/@customminer/norns-three-phase-oscillating-algorithm-based-assets-on-the-bts-dex
Here's the new price feed script repo: https://github.com/BTS-CM/Norns
New parallel price feed script: https://github.com/BTS-CM/Norns/blob/master/parallel_feed.py (change the wss server & min price feed value difference at your discretion).
It would be massively appreciated, thanks 👍
-
Witness Outage explained. A Perfect Storm
During the day & night of 11 - 12 september 2019 my witness stopped producing blocks for several hours, so bad. This is an unforgivable failure and should not have happened, with multiple failovers running and a monitoring script in place to automatically switch.
But still it happened.... What was going on?
It appears a perfect storm happened: Segfaulted main node (?) meh. And my witnessMonitorFailover script got stuck so I did not receive notifications to check. This is the first time in 1000+ days producing blocks.
After investigating it was an outlying coincidence: The server provider on which I have my monitoring script running, had an unexpected maintenance to the vps environment rack (?!!), causing the script to become unresponsive. (FYI i have bitshares related nodes in 3 different providers @ 4 different physical locations).
Most painful thing was that I relied 100% on my failover script. I was missing blocks while literally sitting behind my computer. And even when I launch my browser I have an overview page about witness work opened by default, ... But i didnt launch a new browser... Bummer.
Learning:
- double redundancy on failover scripts or at least a monitoring & notify tool on a second server is not such a bad idea + don't forget to check all nodes before going to bed (!)
Sorry for unwantingly delaying your transactions and I will learn from this.
See you on the chain & thank you for your continued support,
RoelandP
-
So glad... it proves you are a human like us... :)
PS Thanks for your never-ending contributions to bitshares community.
-
Updates: A once in a lifetime trip got me and my family on the road after SteemFest in Bangkok.
Obviously I have been monitoring my services and got help from the monitoring scripts:
1. Once missed 7 blocks in a row before backup switched and continued producing afterwards. It appeared to be a network connectivity issue with the hosting provider.
2. My pricefeed script was outdated and not working according to BAIP2. This has been fixed by installing a brand new pricefeed server. However my BAIP historic feed collection is not complete yet as it just started fresh with collecting and storing feeds, which means my feeds are a little bit off the chart. I expect this to be evened out in the coming 24 hours.
Thank you for your continued support and trust.
-
It took it bit longer but my new feed server is now getting its prices based on past history as far as I can tell. Will need to add binance usdt pair now in the mix.
-
Updated all my nodes to BTS 5.0.0.
-
Updated all my nodes to BTS 5.0.0.
And to 6.0.0 now yeah? How're things going?