The BitShares hangouts are rather technical and thus it's a great time to ask questions. But detailed (n00b) questions are best asked during the afterparty because we don't want to hold up people. In case you missed the hangout you are lucky: I have included good answers by quoting relevant comments from the audience during the hangout. If you have any questions ask here or drop us a line on Discord: https://discord.gg/kbXUQg5
@ash01:57 Excerpt from this weeks Bitshares State of the Network report
05:29 Atomic Swaps between Graphene-based blockchains
The Scorum team would love to join this week's Beyondbitcoin bitshares hangout to discuss atomic cross-chain transactions on the Graphene Framework!
Port ACCT from Scorum · Issue #49 · bitshares/bsips
essentially one transfer within one blockchain only occurs if a second transfer occurs within the other blockchain
The following example might be helpful for readers to demonstrate a use case (this example omits the the technicalities and extra steps that are required):
- One chain (Chain A) has an asset called Apple. Another chain (Chain B) has an asset called Banana.
- Dan has an account on Chain A and B. Nathan also has an account on Chain A and B.
- Dan owns 1 Apple on Chain A. Nathan owns 5 Bananas on Chain B. They want to trade.
- At the end of the ACCT, Dan will own 5 Bananas on Chain B, and Nathan will own 1 Apple on Chain A.
Items to note:
- the traders must have accounts on both blockchains
- an asset never leaves its native blockchain
There is a 48 and 24 hour locking of funds so that they can't be double-spent. 48 hours for the initiator and then 24 for the participant.
A key factor is both parties auditing and agreeing to the terms of the contract, so I guess that it could be changed.
The timing is to allow each party to claim their coins before that ACCT fails and returns back to the original addresses.
38:31 QuantChain specification and build-out
1:03:15 Unified Committee Message regarding Partnerships
https://github.com/BitShares-Committee/Communications/issues/1
Due to continuous misuse of the BitShares Brand name, I propose to publicize the following message, signed via committee-account, please voice your support via a signed message, and/or give feedback in the text used.
Dear BitShares Stakeholders,
Please note that it's impossible to strategically partner, partner, alliance, et patati et patata with BitShares without Stakeholder endorsed voting via the Blockchain.
Any announcements are null and void.
So far only 3 committee members signed this, please highlight this to the community and ask for opinions. Steem: @ash / Discord: fav#1281 / Twitter: btsfav
1:12:52 Trading Bot Worker Proposal
@markopaasila has written a worker proposal for a trading bot for BitShares. More details can be found here.
Some of the benefits for a trading bot are quoted as being:
Please review the worker proposal from inside of your BitShares wallet.
1:14:10 BitShares Quick Reference Guide
A very attractive and helpful Quick Reference Guide about BitShares has been prepared by Aaron/Crypto Fielder and Kevin Messerly/Kimchi King. It categorizes various topics about BitShares and how to use it which should be helpful for many users. Links within each category lead to relevant information all over the Internet.
1:16:10 Accounting Report by BitShares Blockchain Foundation
A detailed 6-month accounting report has been provided by the BitShares Blockchain Foundation (BBF) for various worker proposals that it escrows. The BBF handles workers that are (1) technically paid in BTS, and (2) ultimately paid in bitUSD after valid invoicing by team and conversion of BTS by escrow; excess BTS is later returned to the BTS reserve pool.
Escrow projects include:
Afterparty: Hertz updates:
A warm thanks to 
