My name is @roelandp, a witness for Bitshares since about 1.5 years now. Next to this I am active in the Steem community and organise the annual global conference event SteemFest, this year (edition 3) to be held from 7 to 11 November in Kraków. I've also planned to attend the Bitfest in Amsterdam this weekend and organise a little pancake farewell party on Sunday 23 september actually.

I am proposing this worker (id: 1.14.123), escrowed by the Bitshares Blockchain Foundation, asking for a sponsorship from the Bitshares blockchain for SteemFest3.

The more extensive details of the worker are hosted on BBF workers site, the following is a summary for your consideration.

The Bitshares SteemFest3 sponsorship serves 3 purposes:

SteemFest 3 - 7/8/9/10/11 November - Kraków, Poland
Steem has become the defacto standard blogging tool for (graphene based) blockchain announcements and for example witness announcements of all sorts. Many Steem users know of BitShares and use it, but there is still work to be done. Did you know that just like last year, this year you can also buy your SteemFest ticket with BTS?

SteemFest’s conference program is still in the works but amongst the 2018 speakers who are already confirmed, of whom some of them will also be present:
See steemfest.com for the complete list of announced speakers, which every week adds more on friday’s announcements.

SteemFest 3 sees a varied attendees mix of early crypto adopters and evangelists of the Steem (and related) chains from all over the world with all kinds of profiles. In 2016 (Amsterdam) 208 people attended, in 2017 (Lisbon) 311 people attended. About 25% of the attendees are developers and know their ways in Graphene chain development. People flock in from over 40 countries to Poland this year, about 40% of attendees is female, still quite unique to blockchain / tech conferences.

The sponsorship would entail the following Bitshares integrations with SteemFest:
Risk management:
If the Bitshares community decides this worker aligns and help the BTS chain further, and therefore vote for the worker and trigger the daily payments, I would accept this decision as final and start integrating the Bitshares branding as announced above. One week thereafter the BTS competitions would start - each week a new one. As you can understand this gives me a risk since, once the tickets are given away and/or event materials printed, there is no way to erase them, thus should the voting be redacted / changed towards a 'non paying'/'non-supported' status of this worker afterwards, I am willing to take that risk and cover the funds needed personally. But it would obviously be a less optimal situation.

FYI: BEET-Voting widget integrated on SteemFest.com To support ongoing efforts of the BEET-voting tool, enabling voting-widgets to be scattered anywhere on the web and enable secure voting / blockchain interaction, I have integrated the Worker-proposal 1.14.123 as a widget in the footer of the SteemFest - site.

Thanks to BBF transparent accounting non used vested BTS funds will be returned.

Looking forward to your consideration for a vote!
Should you have any questions feel free to ask below, or ping me on telegram (same username), or maybe we can have a chat during Bitfest in Amsterdam this weekend!

witness bitshares
organiser steemfest Stakeholder Proposals / Worker Proposal 1.14.59 SteemFest Hackathon Bitshares Sponsorship

« on: September 04, 2017, 09:09:43 pm »
Fellow community members,

As some of you may know, last year I organised the inaugural edition of SteemFest in Amsterdam which drew 200 steem users and crypto lovers from more than 30 countries for 3 days of fun, talks and more fun. This year we are going to do it all over again, but then in Lisbon on 1/2/3/4/5 November (and if all works out nicely some more people - ticketsales are on track).

As I regularly organise hackathons in the fiat world, and am a developer myself (and a bitshares witness), I felt the strong urge to use the opportunity of using SteemFest's rising reach to launch the event with a hackathon on 1 November.

The SteemFest hackathon is open to apps running on any blockchain, but has a bias towards Graphene As long as teams / participants are able to present their works on Friday November 3 (2nd conference day), in person, they are eligible to join with any blockchain based app.

For the hackathon specifically I envisioned having a couple of "Focus Chains" - these chains get extra attention in the announcements and are offered a change to give away their own prize and judging criteria in order to attract developers to build a proof of concept app for them. Additionally a Focus Chain gets a morning slot at the hackathon kickoff (dev oriented quick pitch) and a 20 minute slot at the generic SteemFest Conference days. Both are ways to:

The worker proposal will be submitted with the help of (and through) the Bitshares.Foundation and I will let you know once it is up and ready for voting. For now I invite you to check the more in-depth proposal (with funds requested and intended use as well as a preview link to the Hackathon dedicated site) which is already distributed at the foundation's site:  http://www.bitshares.foundation/workers/2017-09-steemfest

I hope you like this proposal, will consider to support it by voting on 1.14.59 and I am happy to answer your questions, either here or through telegram [member=43607]roelandp[/member]

General Discussion / (Witness) Tool: Server Stats to Telegram

« on: May 08, 2017, 12:02:36 am »
Here is a little tool I made to get an automated report of server Key Performance Indicators at my morning coffee, delivered via Telegram. This can come in useful for witnesses to have a finger on their server's performance.

What this script does is checking and reporting:
* Disk Space (free / used)
* CPU usage per core
* Ram space (free / used)

Collects it and sends it as a Telegram message. Simply configure a cronjob to get the report as often as you like.

Depends on psutil, requests an os packages for Python3. Check out the script on my github:

Stakeholder Proposals / Tool / website: Bitshares Witness Log

« on: May 01, 2017, 10:13:47 pm »
Last week I released a witness monitor tool, meant for personal usage by witnesses, to monitor the availability of seednode, pricefeed latency in updates and missing blocks. From various members I received requests to expand on that monitoring tool and start to log the data and turn it into a Bitshares Witness Log. I found it a challenge in my python skills, so I sharpened my knife: * Update Frequency
Three times per hour (2nd,22nd,42nd minute) the backend checks this witness data by using Python-Bitshares (thank you [member=120]xeroc[/member]!) and storing it in an MySQL database.

Three times per hour (5th, 25th, 45th minute) the backend publishes a new version as a static JSONP file with the latest data details as compiled from this database as a source-feed for this overview, using Bootstrap-Table to display it. This means the data you see can be maximum 23 minutes old before fresh data is displayed. If this is not the case and the top "last updated at" mentions way more time since that, please notify me as my server must have crashed!

Insights & Analyse
Click here to go to the Bitshares Witness Log

ps: I know I am a very new witness, and I don't want to be telling anyone what to do, I feel humble in my position: nonetheless I noticed that some of the witnesses are missing their 'urls'-part in the witness entry. Would be great if you could 'update_witness' with an URL![/list]

General Discussion / Witness Monitoring Script based on websocket connection only (Python Bitshares)

« on: April 24, 2017, 08:38:52 pm »
Yes! I got voted in the active witness list! (here is my proposal) Thanks for your support!!! I immediately started my feed publishing more intense (twice per hour) and will continue to add more price feeds.

This morning I took the time to write a Witness Monitoring Script to monitor my witness main tasks on an independent server, powered by [member=120]xeroc[/member] 's Python Bitshares libraries (he just release 0.1.5!) for python3.

The script provides the monitoring of 3 core witness tasks and reports via a telegram bot API call the following:

1. Monitor missing blocks
Whenever a new block is missed you will get a notification. This part of the script can (and will) be extended towards automated switching to the backup witness signing key once a threshold is passed.

2. Monitor the availability of your public seednode
By utilising the telnet library the script tries to connect to the given seednode and will report on time-out or errors.

3. Monitor the publishing of a set of assets' pricefeed(s)
By requesting the asset's feeds and checking against your witness name (configurable) the script keeps monitoring how long since you posted the given asset's feed. Whenever the configurable threshold in hours has passed and you have not yet published a new feed for the asset, you will get a notification.

Check it out on Github!
Let me know your thoughts, remarks, or requests.

Stakeholder Proposals / [Witness Proposal] 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.

My name is RoelandP from Amsterdam. I am a developer of (mostly) mobile apps 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. Since about 2003 I make a living by making sites & apps and some photoshopping / designing for my  parents' pancake restaurant 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.

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 [member=6601]wackou[/member]'s seednode statuspage and hardcoded in the bitshares sourcecode)

My current server portfolio setup for Bitshares is as follows:

Public Seed:

Witness signing server:

Backup witness signing server:

Backup Seed:

Public Websocket node - btsws.roelandp.nl/ws:

Test VPS's readily available:

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 [member=120]xeroc[/member] and together with [member=2186]iHashFury[/member] 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?

Can I have your vote? Vote roelandp
Ask me questions here or ping me directly via:

Proof of Face:

To Jupiter's Moon! [/list][/list]

Page created in 0.091 seconds with 18 queries.
[null, null, {"document_url": "https://bitsharestalk.org/index.php?action=profile;area=showposts;sa=topics;u=43607", "unformatted_src": "https://steemfest.com/img/steemfestopengraph.jpg", "src": "https://steemfest.com/img/steemfestopengraph.jpg", "formatted_filename": "steemfestopengraph", "rendered_width": 867, "rendered_height": 500}, null, null, {"document_url": "https://bitsharestalk.org/index.php?action=profile;area=showposts;sa=topics;u=43607", "unformatted_src": "http://i.imgur.com/fB89dnal.png", "src": "http://i.imgur.com/fB89dnal.png", "formatted_filename": "fB dnal", "rendered_width": 272, "rendered_height": 367}, null, {"document_url": "https://bitsharestalk.org/index.php?action=profile;area=showposts;sa=topics;u=43607", "unformatted_src": "http://i.imgur.com/KKgPCRT.png", "src": "http://i.imgur.com/KKgPCRT.png", "formatted_filename": "KKgPCRT", "rendered_width": 850, "rendered_height": 711}, null, null]