BitShares Hangout #28 - 2017-07-07 - OpenSource Agenda [WhaleShare and BeyondBit Payments Based on Post Payouts!]

in #beyondbitcoin7 years ago (edited)


BitShares Hangouts Speakers and Worker Proposals Earn WhaleShares for Participating!

Use them to hire attendees and listeners to promote your work!





Notice: WhaleShares Payouts are based on go out After Final Payouts occur on this Post



These tokens are on BitShares! So make sure you have a BitShares Wallet to receive and send them for upvotes on your steem posts!

Download BitShares Wallet



"Join weekly to speak with founding community members of the BitShares Enterprise Dex about history and current events in Cryptocurrency and earn some free BitShares Tokens!" ~@officialfuzzy

The Format of these Hangouts:

This will go up every Thursday the day before the BitShares Hangout. BitShares community members who post subjects to cover and bring topics of discussion are asked to do so in response to this post first. Worker Proposals are a Chief Focus in these hangouts, but other topics and projects are welcome to join. @officialfuzzy can finally pay people who have supported this powerful cryptocurrency for the past 4 years since its birth and evolution. So reply below with valuable topics, updates, info we should cover and earn upvotes from in this thread and earn a special bonus if yours are chosen!


How much time will we have?

Hangouts will be at least 45 minutes long, but depending on attendance and projects/topics to be covered may last up to 1 hour. Given this, we will try to stay with 4-5 core topics and will fit in others where possible.


What will we earn for contributing?

Those who attend will each earn from a pool of bitshares that will be purchased with earnings from this post. They will then be given directly to you via our new guestbook that we are testing.
Fuzzy will be giving whaleshares to community founders who attend this weekly hangout to give their own unique perspectives and expert commentary. He will also be giving them to people who give topics and information we choose to use in our hangout!

So make sure you get a BitShares Wallet!

And let's not forget...you get SP through upvoting quality information and content worth sharing with the top minds in crypto across the graphene ecosystem!


Is any topic off Limits?

Yes. We reserve the right to learn from the newest trickster trolling steemit consistently searching for way to insert chaos into the equation and devise future strategies for negating these. Naturally if these efforts become ham-fisted attempts at shutting down free speech in honest conversations, the audience will hold us accountable.
But with that said....pretty much anything can be covered--even up to and including current events. However, I personally will only be voting up stories that touch the blockchain in some way shape or form and will be asking the community to downvote absolute Rubbish! ;)



Listen to Last Week's Hangout!



How to Join



Step 1: Download Mumble Here

Step 2: Watch Setup Instructions

Step 3:

Enter the following information:

Label: BeyondBitcoin om
Address: 149.210.187.155
Port: 64738
Username: Enter your username
Password: w0rldCh@NG3rsUN!t3



During the Week you can find us in Our 24/7 WhaleShares Server! (preferably the Adult Swim VOIP)



All BeyondBitcoin content is powered by Steemit.com so please join the new social media movement that enables Creative Commons content creators and Open Source developers to earn funding for participating in the community's growth and sustenance. Post to Steemit.com to earn and pay others with a simple upvote!

Sort:  

please ask witnesses in call (I won't make it)

  • how are you avoiding dangerous feed errors in case of bitcoin fork?
  • are there plans to hold bitBTC prior to 1st of august?

Relevant BSIP in case of bitBTC global settlement:

A good question is: What fork will bitBTC reference after the split?

Preferably, we shouldn't reference the 'UASF' fork.

A good question is: What fork will bitBTC reference after the split?

I'd prefer UASF though. But it doesn't matter that much, since bitBTC is just a minor side product in our company... we just need to avoid negative news, eventually affecting all smartcoins, because we did not react in time

I prefer the big-block approach as originally intended by Satoshi; off-chain solutions are a neat idea on top of the Bitcoin blockchain, but strangling the core scaling mechanism (increasing block size) to push everyone onto blockstream's off-chain scaling solution is a terrible idea.

UASF by definition is a sybill attack, they're even proposing changing POW mechanisms which is really a scorched earth policy for BTC!

On the upside, we may experience the 'flippening' where BTC loses its #1 place, if this happens who knows what will happen in the crypto markets?! Exciting times!

Awesome and upvoted!

Her here!
Awesome and upvoted !!

I will be giving an update on my campaign as a proxy as well as the following worker campaigns:

  1. Update on User Interface for Easily Submitting Preliminary Worker Proposals.
    1a) The Plan is that if we can create enough traction to continue, that we choose a random week out of every month for 4 months to retrieve data on the difference between workers incoming during and after these advertising campaigns.
  2. CoinMarketcap Advertisement in the top banner to pay for a "the blockchain is hiring" = 6-7k for a week.

On a similar topic of UI & worker proposals, here's the latest BTS-UI compiled code:

Unfortunately though, there hasn't been a core nor UI release which has included this change yet, additionally the Bitshares.org downloads page is displaying links to old releases.

CoinMarketcap Advertisement in the top banner to pay for a "the blockchain is hiring" = 6-7k for a week.

Sounds great to me, you've got my vote when you create the worker proposal! :)

I'd like to give a quick shout out to a couple of the recent BSIPs that I have written up:

I've been using #Whaleshares and #Beyondbits to upvote these BSIPs so that I've been able to focus on writing them more or less full time :D

Best regards,
@cm-steem

Wasn't there an idea to setup up some bounty for ideas people want to see implemented? I'm currently learning the bitshares wallet codebase by trying to fix up the invoice UI, but after that I'm going to be looking for ideas people want implemented. I've not yet accrued enough BTS to submit a worker but having a list of things I could work on to show the community what I can offer would be great.

Wasn't there an idea to setup up some bounty for ideas people want to see implemented?

There was the suggestion that by proposing a bounty, we can advertise the need for developers to complete a task for the Bitshares network, rather than waiting for a dev to take notice and gather the confidence to create a worker proposal, however there's not a bounty mechanism within the client.

Fuzzy is talking about a similar topic this week.

The Bitshares-UI has integrated the ability to create workers via the gui, but the latest client release isn't new enough to include this change..

Hey @officialfuzzy!

Unless you've changed day of the week I guess your supposed to mean 2017-07-07 😎

Looking forward to yet another "blow-my-mind crypto hangout" as always.

Sadly having to wait to the Raw recording getting published since work keeps me busy st the time of this, DAMN YOU WORK 😭

LOL...i specifically remember looking at the date now that u say that...and putting in todays. Thnx mate ;)

It's what I do, we are here to back each others in any tiny way we can 😉

Good luck mate!

informative and spectacular :)

Thanks for sharing this important info

This comment has received a 0.15 % upvote from @booster thanks to: @hamzaoui.

Reviving Black-Swanned Assets

I second what @cm-steem has brought up regarding reviving black-swanned assets. In my opinion, this item should have medium to high priority both to revive past assets that have been affected (Ruble, Gridcoin, etc.), and to be ready to handle any future black swans that might occur. Imagine the bad impression on BitShares if a higher visibility asset gets black-swanned and cannot be revived quickly.

Issue on GitHub
BSIP-0017 : Revive BitAssets after global settlement
BSIP-0018 : Revive BitAsset through buying Settlement Pool