Bitcoin Internals A Technical Guide To Bitcoin [PDF]

Internal FBI risk assessment of Bitcoin network (pdf, 24 April 2012)

submitted by EquanimousMind to evolutionReddit [link] [comments]

US OFAC issues advisory: ransom payments for ransomware may involve felony charges and personal civil liability for staff.

Relevant Excerpt:
Under the authority of the International Emergency Economic Powers Act (IEEPA) or the Trading with the Enemy Act (TWEA),9 U.S. persons are generally prohibited from engaging in transactions, directly or indirectly, with individuals or entities (“persons”) on OFAC’s Specially Designated Nationals and Blocked Persons List (SDN List), other blocked persons, and those covered by comprehensive country or region embargoes (e.g., Cuba, the Crimea region of Ukraine, Iran, North Korea, and Syria). Additionally, any transaction that causes a violation under IEEPA, including transactions by a non-U.S. person which causes a U.S. person to violate any IEEPA-based sanctions, is also prohibited. U.S. persons, wherever located, are also generally prohibited from facilitating actions of non-U.S. persons, which could not be directly performed by U.S. persons due to U.S. sanctions regulations. OFAC may impose civil penalties for sanctions violations based on strict liability, meaning that a person subject to U.S. jurisdiction may be held civilly liable even if it did not know or have reason to know it was engaging in a transaction with a person that is prohibited under sanctions laws and regulations administered by OFAC.
Sauce Here: https://home.treasury.gov/system/files/126/ofac_ransomware_advisory_10012020_1.pdf
OFAC Sanctions list here: https://sanctionssearch.ofac.treas.gov/
Analysis: Both TWEA and IEEPA carries Criminal and Civil penalties, so under these acts they can fine the company, fine staff directly, or press criminal charges. We know the US Government as part of both the 5 eyes agreements and domestic bank monitoring programs under FACTA monitors all international wire transfers. Bitcoin and other cryptocurrencies generally leave a paper trail that can be traced back to who purchased the currency.
What I expect to start happening here is most CFO's are going to write off the cost of the ransom as a tax deduction which tips off the IRS that a ransom of some kind was paid. I expect the next step is the IRS is going to start asking for additional proof of payment and additional information about the cases. That puts CFO's in a bind, because I expect both the IRS, and federal courts, won't let it fly that you didn't know who you were paying money to under the TWEA. They'll sit on the data, and when eventually an APT Group gets compromised, they'll trace the payments back via said tax records. At that point, if your org paid under this, that data gets used to open up a search warrant and then they rip you a new one especially if the payment was substantial.
The bigger issue here is it opens up tremendous liability for security services firms and insurers who pay ransoms on behalf of clients or advise clients to pay ransoms.
Now is a good time to review your backup strategy and ensure you have tested backups that are isolated from your infrastructure.
For those of you with your hands tied behind your back, now is a good time to gently remind your management staff, and especially the CFO if you have their ear, that they cannot rely on the renound cryptographic competence of our eastern european bretheren, and that their worst-case risk is a determined remote attacker and adversary of the US infecting your network, destroying the data while making it look like a ransomware attack, selling you worthless encryption keys to fund their operation before flaunting the fact they took you for a fool with a press release taking credit for the attack to tip off state government you paid them in order to further disrupt the company operations via putting your talented technical staff or c-suite staff in handcuffs and injuring your PR.
To those of you in the business who are afraid of being scapegoated or in a tenuous situation, getchu some evidence tape and some tags, some vanilla envelopes and a glue stick. Print 2 copies, put one copy in a folder, seal it with evidence tape and a tag, then use your handy glue stick to adhere the other vanilla folder to its back and put the 2nd copy in so you can review the paperwork without breaking the evidence seal and shove that sucker in a fire proof safe or safety deposit box. Also, Mailstore home is free.
TL;DR: If your company is attacked by ransomware, tell the management only facts of the occurance you know, what you can and cannot do for them, and don't advise them of anything upto and including getting a security services firm involved. I wouldn't even tell them paying the ransom might work. If you're going to have a verbal conversation, make it a one-on-one.
Happy Saturday all!
submitted by JohnWickBOFH to sysadmin [link] [comments]

The Atari VCS is mostly a U.S. product, while Atari Token cannot be purchased in the U.S. by most people.

A lot of the recent "news" emphasizes that the token cannot be purchased or traded in the US. The Bloomberg article for example, said "On Oct. 29, Bitcoin.com Exchange will start selling $1 million worth of Atari Tokens for 25 cents apiece to retail investors outside of the U.S. The tokens will be used for in-game purchases and for partner games..."
Sure enough, the Atari Token purchase agreement (pdf) specifically stipulates that the "purchaser is not a citizen or resident of ... the United States of America, People's Republic of China, or South Korea." There is an exception. It appears they will sell you Atari Token if you claim to be an accredited investor (which means you are rich enough to have money to burn). So... Why would an American accredited investor buy a token which cannot be legally traded?
The VCS is mainly targeted to the US market. It could be pre-ordered in the US, Australia, and New Zealand, but even if the crowdfunding campaign was international, the majority of people buying the console cannot legally use the Atari Token. If you cannot legally purchase it, you cannot legally use it for "in-game purchases".
My understanding is that crypto-types usually ignore these laws and either pretend they are anonymous, or lie about themselves. In shady markets, this sort of works, sometimes, for a while, but due to the lack of federal manpower, not because the feds don't know this is happening. When a government agency decides to enforce these laws, like with Atari's "partner" Unikrn or even more recently with BitMex, it ends very badly.
submitted by ComradeSnuggles to AtariVCS [link] [comments]

Dragonchain Great Reddit Scaling Bake-Off Public Proposal

Dragonchain Great Reddit Scaling Bake-Off Public Proposal

Dragonchain Public Proposal TL;DR:

Dragonchain has demonstrated twice Reddit’s entire total daily volume (votes, comments, and posts per Reddit 2019 Year in Review) in a 24-hour demo on an operational network. Every single transaction on Dragonchain is decentralized immediately through 5 levels of Dragon Net, and then secured with combined proof on Bitcoin, Ethereum, Ethereum Classic, and Binance Chain, via Interchain. At the time, in January 2020, the entire cost of the demo was approximately $25K on a single system (transaction fees locked at $0.0001/txn). With current fees (lowest fee $0.0000025/txn), this would cost as little as $625.
Watch Joe walk through the entire proposal and answer questions on YouTube.
This proposal is also available on the Dragonchain blog.

Hello Reddit and Ethereum community!

I’m Joe Roets, Founder & CEO of Dragonchain. When the team and I first heard about The Great Reddit Scaling Bake-Off we were intrigued. We believe we have the solutions Reddit seeks for its community points system and we have them at scale.
For your consideration, we have submitted our proposal below. The team at Dragonchain and I welcome and look forward to your technical questions, philosophical feedback, and fair criticism, to build a scaling solution for Reddit that will empower its users. Because our architecture is unlike other blockchain platforms out there today, we expect to receive many questions while people try to grasp our project. I will answer all questions here in this thread on Reddit, and I've answered some questions in the stream on YouTube.
We have seen good discussions so far in the competition. We hope that Reddit’s scaling solution will emerge from The Great Reddit Scaling Bake-Off and that Reddit will have great success with the implementation.

Executive summary

Dragonchain is a robust open source hybrid blockchain platform that has proven to withstand the passing of time since our inception in 2014. We have continued to evolve to harness the scalability of private nodes, yet take full advantage of the security of public decentralized networks, like Ethereum. We have a live, operational, and fully functional Interchain network integrating Bitcoin, Ethereum, Ethereum Classic, and ~700 independent Dragonchain nodes. Every transaction is secured to Ethereum, Bitcoin, and Ethereum Classic. Transactions are immediately usable on chain, and the first decentralization is seen within 20 seconds on Dragon Net. Security increases further to public networks ETH, BTC, and ETC within 10 minutes to 2 hours. Smart contracts can be written in any executable language, offering full freedom to existing developers. We invite any developer to watch the demo, play with our SDK’s, review open source code, and to help us move forward. Dragonchain specializes in scalable loyalty & rewards solutions and has built a decentralized social network on chain, with very affordable transaction costs. This experience can be combined with the insights Reddit and the Ethereum community have gained in the past couple of months to roll out the solution at a rapid pace.

Response and PoC

In The Great Reddit Scaling Bake-Off post, Reddit has asked for a series of demonstrations, requirements, and other considerations. In this section, we will attempt to answer all of these requests.

Live Demo

A live proof of concept showing hundreds of thousands of transactions
On Jan 7, 2020, Dragonchain hosted a 24-hour live demonstration during which a quarter of a billion (250 million+) transactions executed fully on an operational network. Every single transaction on Dragonchain is decentralized immediately through 5 levels of Dragon Net, and then secured with combined proof on Bitcoin, Ethereum, Ethereum Classic, and Binance Chain, via Interchain. This means that every single transaction is secured by, and traceable to these networks. An attack on this system would require a simultaneous attack on all of the Interchained networks.
24 hours in 4 minutes (YouTube):
24 hours in 4 minutes
The demonstration was of a single business system, and any user is able to scale this further, by running multiple systems simultaneously. Our goals for the event were to demonstrate a consistent capacity greater than that of Visa over an extended time period.
Tooling to reproduce our demo is available here:
https://github.com/dragonchain/spirit-bomb

Source Code

Source code (for on & off-chain components as well tooling used for the PoC). The source code does not have to be shared publicly, but if Reddit decides to use a particular solution it will need to be shared with Reddit at some point.

Scaling

How it works & scales

Architectural Scaling

Dragonchain’s architecture attacks the scalability issue from multiple angles. Dragonchain is a hybrid blockchain platform, wherein every transaction is protected on a business node to the requirements of that business or purpose. A business node may be held completely private or may be exposed or replicated to any level of exposure desired.
Every node has its own blockchain and is independently scalable. Dragonchain established Context Based Verification as its consensus model. Every transaction is immediately usable on a trust basis, and in time is provable to an increasing level of decentralized consensus. A transaction will have a level of decentralization to independently owned and deployed Dragonchain nodes (~700 nodes) within seconds, and full decentralization to BTC and ETH within minutes or hours. Level 5 nodes (Interchain nodes) function to secure all transactions to public or otherwise external chains such as Bitcoin and Ethereum. These nodes scale the system by aggregating multiple blocks into a single Interchain transaction on a cadence. This timing is configurable based upon average fees for each respective chain. For detailed information about Dragonchain’s architecture, and Context Based Verification, please refer to the Dragonchain Architecture Document.

Economic Scaling

An interesting feature of Dragonchain’s network consensus is its economics and scarcity model. Since Dragon Net nodes (L2-L4) are independent staking nodes, deployment to cloud platforms would allow any of these nodes to scale to take on a large percentage of the verification work. This is great for scalability, but not good for the economy, because there is no scarcity, and pricing would develop a downward spiral and result in fewer verification nodes. For this reason, Dragonchain uses TIME as scarcity.
TIME is calculated as the number of Dragons held, multiplied by the number of days held. TIME influences the user’s access to features within the Dragonchain ecosystem. It takes into account both the Dragon balance and length of time each Dragon is held. TIME is staked by users against every verification node and dictates how much of the transaction fees are awarded to each participating node for every block.
TIME also dictates the transaction fee itself for the business node. TIME is staked against a business node to set a deterministic transaction fee level (see transaction fee table below in Cost section). This is very interesting in a discussion about scaling because it guarantees independence for business implementation. No matter how much traffic appears on the entire network, a business is guaranteed to not see an increased transaction fee rate.

Scaled Deployment

Dragonchain uses Docker and Kubernetes to allow the use of best practices traditional system scaling. Dragonchain offers managed nodes with an easy to use web based console interface. The user may also deploy a Dragonchain node within their own datacenter or favorite cloud platform. Users have deployed Dragonchain nodes on-prem on Amazon AWS, Google Cloud, MS Azure, and other hosting platforms around the world. Any executable code, anything you can write, can be written into a smart contract. This flexibility is what allows us to say that developers with no blockchain experience can use any code language to access the benefits of blockchain. Customers have used NodeJS, Python, Java, and even BASH shell script to write smart contracts on Dragonchain.
With Docker containers, we achieve better separation of concerns, faster deployment, higher reliability, and lower response times.
We chose Kubernetes for its self-healing features, ability to run multiple services on one server, and its large and thriving development community. It is resilient, scalable, and automated. OpenFaaS allows us to package smart contracts as Docker images for easy deployment.
Contract deployment time is now bounded only by the size of the Docker image being deployed but remains fast even for reasonably large images. We also take advantage of Docker’s flexibility and its ability to support any language that can run on x86 architecture. Any image, public or private, can be run as a smart contract using Dragonchain.

Flexibility in Scaling

Dragonchain’s architecture considers interoperability and integration as key features. From inception, we had a goal to increase adoption via integration with real business use cases and traditional systems.
We envision the ability for Reddit, in the future, to be able to integrate alternate content storage platforms or other financial services along with the token.
  • LBRY - To allow users to deploy content natively to LBRY
  • MakerDAO to allow users to lend small amounts backed by their Reddit community points.
  • STORJ/SIA to allow decentralized on chain storage of portions of content. These integrations or any other are relatively easy to integrate on Dragonchain with an Interchain implementation.

Cost

Cost estimates (on-chain and off-chain) For the purpose of this proposal, we assume that all transactions are on chain (posts, replies, and votes).
On the Dragonchain network, transaction costs are deterministic/predictable. By staking TIME on the business node (as described above) Reddit can reduce transaction costs to as low as $0.0000025 per transaction.
Dragonchain Fees Table

Getting Started

How to run it
Building on Dragonchain is simple and requires no blockchain experience. Spin up a business node (L1) in our managed environment (AWS), run it in your own cloud environment, or on-prem in your own datacenter. Clear documentation will walk you through the steps of spinning up your first Dragonchain Level 1 Business node.
Getting started is easy...
  1. Download Dragonchain’s dctl
  2. Input three commands into a terminal
  3. Build an image
  4. Run it
More information can be found in our Get started documents.

Architecture
Dragonchain is an open source hybrid platform. Through Dragon Net, each chain combines the power of a public blockchain (like Ethereum) with the privacy of a private blockchain.
Dragonchain organizes its network into five separate levels. A Level 1, or business node, is a totally private blockchain only accessible through the use of public/private keypairs. All business logic, including smart contracts, can be executed on this node directly and added to the chain.
After creating a block, the Level 1 business node broadcasts a version stripped of sensitive private data to Dragon Net. Three Level 2 Validating nodes validate the transaction based on guidelines determined from the business. A Level 3 Diversity node checks that the level 2 nodes are from a diverse array of locations. A Level 4 Notary node, hosted by a KYC partner, then signs the validation record received from the Level 3 node. The transaction hash is ledgered to the Level 5 public chain to take advantage of the hash power of massive public networks.
Dragon Net can be thought of as a “blockchain of blockchains”, where every level is a complete private blockchain. Because an L1 can send to multiple nodes on a single level, proof of existence is distributed among many places in the network. Eventually, proof of existence reaches level 5 and is published on a public network.

API Documentation

APIs (on chain & off)

SDK Source

Nobody’s Perfect

Known issues or tradeoffs
  • Dragonchain is open source and even though the platform is easy enough for developers to code in any language they are comfortable with, we do not have so large a developer community as Ethereum. We would like to see the Ethereum developer community (and any other communities) become familiar with our SDK’s, our solutions, and our platform, to unlock the full potential of our Ethereum Interchain. Long ago we decided to prioritize both Bitcoin and Ethereum Interchains. We envision an ecosystem that encompasses different projects to give developers the ability to take full advantage of all the opportunities blockchain offers to create decentralized solutions not only for Reddit but for all of our current platforms and systems. We believe that together we will take the adoption of blockchain further. We currently have additional Interchain with Ethereum Classic. We look forward to Interchain with other blockchains in the future. We invite all blockchains projects who believe in decentralization and security to Interchain with Dragonchain.
  • While we only have 700 nodes compared to 8,000 Ethereum and 10,000 Bitcoin nodes. We harness those 18,000 nodes to scale to extremely high levels of security. See Dragonchain metrics.
  • Some may consider the centralization of Dragonchain’s business nodes as an issue at first glance, however, the model is by design to protect business data. We do not consider this a drawback as these nodes can make any, none, or all data public. Depending upon the implementation, every subreddit could have control of its own business node, for potential business and enterprise offerings, bringing new alternative revenue streams to Reddit.

Costs and resources

Summary of cost & resource information for both on-chain & off-chain components used in the PoC, as well as cost & resource estimates for further scaling. If your PoC is not on mainnet, make note of any mainnet caveats (such as congestion issues).
Every transaction on the PoC system had a transaction fee of $0.0001 (one-hundredth of a cent USD). At 256MM transactions, the demo cost $25,600. With current operational fees, the same demonstration would cost $640 USD.
For the demonstration, to achieve throughput to mimic a worldwide payments network, we modeled several clients in AWS and 4-5 business nodes to handle the traffic. The business nodes were tuned to handle higher throughput by adjusting memory and machine footprint on AWS. This flexibility is valuable to implementing a system such as envisioned by Reddit. Given that Reddit’s daily traffic (posts, replies, and votes) is less than half that of our demo, we would expect that the entire Reddit system could be handled on 2-5 business nodes using right-sized containers on AWS or similar environments.
Verification was accomplished on the operational Dragon Net network with over 700 independently owned verification nodes running around the world at no cost to the business other than paid transaction fees.

Requirements

Scaling

This PoC should scale to the numbers below with minimal costs (both on & off-chain). There should also be a clear path to supporting hundreds of millions of users.
Over a 5 day period, your scaling PoC should be able to handle:
*100,000 point claims (minting & distributing points) *25,000 subscriptions *75,000 one-off points burning *100,000 transfers
During Dragonchain’s 24 hour demo, the above required numbers were reached within the first few minutes.
Reddit’s total activity is 9000% more than Ethereum’s total transaction level. Even if you do not include votes, it is still 700% more than Ethereum’s current volume. Dragonchain has demonstrated that it can handle 250 million transactions a day, and it’s architecture allows for multiple systems to work at that level simultaneously. In our PoC, we demonstrate double the full capacity of Reddit, and every transaction was proven all the way to Bitcoin and Ethereum.
Reddit Scaling on Ethereum

Decentralization

Solutions should not depend on any single third-party provider. We prefer solutions that do not depend on specific entities such as Reddit or another provider, and solutions with no single point of control or failure in off-chain components but recognize there are numerous trade-offs to consider
Dragonchain’s architecture calls for a hybrid approach. Private business nodes hold the sensitive data while the validation and verification of transactions for the business are decentralized within seconds and secured to public blockchains within 10 minutes to 2 hours. Nodes could potentially be controlled by owners of individual subreddits for more organic decentralization.
  • Billing is currently centralized - there is a path to federation and decentralization of a scaled billing solution.
  • Operational multi-cloud
  • Operational on-premises capabilities
  • Operational deployment to any datacenter
  • Over 700 independent Community Verification Nodes with proof of ownership
  • Operational Interchain (Interoperable to Bitcoin, Ethereum, and Ethereum Classic, open to more)

Usability Scaling solutions should have a simple end user experience.

Users shouldn't have to maintain any extra state/proofs, regularly monitor activity, keep track of extra keys, or sign anything other than their normal transactions
Dragonchain and its customers have demonstrated extraordinary usability as a feature in many applications, where users do not need to know that the system is backed by a live blockchain. Lyceum is one of these examples, where the progress of academy courses is being tracked, and successful completion of courses is rewarded with certificates on chain. Our @Save_The_Tweet bot is popular on Twitter. When used with one of the following hashtags - #please, #blockchain, #ThankYou, or #eternalize the tweet is saved through Eternal to multiple blockchains. A proof report is available for future reference. Other examples in use are DEN, our decentralized social media platform, and our console, where users can track their node rewards, view their TIME, and operate a business node.
Examples:

Transactions complete in a reasonable amount of time (seconds or minutes, not hours or days)
All transactions are immediately usable on chain by the system. A transaction begins the path to decentralization at the conclusion of a 5-second block when it gets distributed across 5 separate community run nodes. Full decentralization occurs within 10 minutes to 2 hours depending on which interchain (Bitcoin, Ethereum, or Ethereum Classic) the transaction hits first. Within approximately 2 hours, the combined hash power of all interchained blockchains secures the transaction.

Free to use for end users (no gas fees, or fixed/minimal fees that Reddit can pay on their behalf)
With transaction pricing as low as $0.0000025 per transaction, it may be considered reasonable for Reddit to cover transaction fees for users.
All of Reddit's Transactions on Blockchain (month)
Community points can be earned by users and distributed directly to their Reddit account in batch (as per Reddit minting plan), and allow users to withdraw rewards to their Ethereum wallet whenever they wish. Withdrawal fees can be paid by either user or Reddit. This model has been operating inside the Dragonchain system since 2018, and many security and financial compliance features can be optionally added. We feel that this capability greatly enhances user experience because it is seamless to a regular user without cryptocurrency experience, yet flexible to a tech savvy user. With regard to currency or token transactions, these would occur on the Reddit network, verified to BTC and ETH. These transactions would incur the $0.0000025 transaction fee. To estimate this fee we use the monthly active Reddit users statista with a 60% adoption rate and an estimated 10 transactions per month average resulting in an approximate $720 cost across the system. Reddit could feasibly incur all associated internal network charges (mining/minting, transfer, burn) as these are very low and controllable fees.
Reddit Internal Token Transaction Fees

Reddit Ethereum Token Transaction Fees
When we consider further the Ethereum fees that might be incurred, we have a few choices for a solution.
  1. Offload all Ethereum transaction fees (user withdrawals) to interested users as they wish to withdraw tokens for external use or sale.
  2. Cover Ethereum transaction fees by aggregating them on a timed schedule. Users would request withdrawal (from Reddit or individual subreddits), and they would be transacted on the Ethereum network every hour (or some other schedule).
  3. In a combination of the above, customers could cover aggregated fees.
  4. Integrate with alternate Ethereum roll up solutions or other proposals to aggregate minting and distribution transactions onto Ethereum.

Bonus Points

Users should be able to view their balances & transactions via a blockchain explorer-style interface
From interfaces for users who have no knowledge of blockchain technology to users who are well versed in blockchain terms such as those present in a typical block explorer, a system powered by Dragonchain has flexibility on how to provide balances and transaction data to users. Transactions can be made viewable in an Eternal Proof Report, which displays raw data along with TIME staking information and traceability all the way to Bitcoin, Ethereum, and every other Interchained network. The report shows fields such as transaction ID, timestamp, block ID, multiple verifications, and Interchain proof. See example here.
Node payouts within the Dragonchain console are listed in chronological order and can be further seen in either Dragons or USD. See example here.
In our social media platform, Dragon Den, users can see, in real-time, their NRG and MTR balances. See example here.
A new influencer app powered by Dragonchain, Raiinmaker, breaks down data into a user friendly interface that shows coin portfolio, redeemed rewards, and social scores per campaign. See example here.

Exiting is fast & simple
Withdrawing funds on Dragonchain’s console requires three clicks, however, withdrawal scenarios with more enhanced security features per Reddit’s discretion are obtainable.

Interoperability Compatibility with third party apps (wallets/contracts/etc) is necessary.
Proven interoperability at scale that surpasses the required specifications. Our entire platform consists of interoperable blockchains connected to each other and traditional systems. APIs are well documented. Third party permissions are possible with a simple smart contract without the end user being aware. No need to learn any specialized proprietary language. Any code base (not subsets) is usable within a Docker container. Interoperable with any blockchain or traditional APIs. We’ve witnessed relatively complex systems built by engineers with no blockchain or cryptocurrency experience. We’ve also demonstrated the creation of smart contracts within minutes built with BASH shell and Node.js. Please see our source code and API documentation.

Scaling solutions should be extensible and allow third parties to build on top of it Open source and extensible
APIs should be well documented and stable

Documentation should be clear and complete
For full documentation, explore our docs, SDK’s, Github repo’s, architecture documents, original Disney documentation, and other links or resources provided in this proposal.

Third-party permissionless integrations should be possible & straightforward Smart contracts are Docker based, can be written in any language, use full language (not subsets), and can therefore be integrated with any system including traditional system APIs. Simple is better. Learning an uncommon or proprietary language should not be necessary.
Advanced knowledge of mathematics, cryptography, or L2 scaling should not be required. Compatibility with common utilities & toolchains is expected.
Dragonchain business nodes and smart contracts leverage Docker to allow the use of literally any language or executable code. No proprietary language is necessary. We’ve witnessed relatively complex systems built by engineers with no blockchain or cryptocurrency experience. We’ve also demonstrated the creation of smart contracts within minutes built with BASH shell and Node.js.

Bonus

Bonus Points: Show us how it works. Do you have an idea for a cool new use case for Community Points? Build it!

TIME

Community points could be awarded to Reddit users based upon TIME too, whereas the longer someone is part of a subreddit, the more community points someone naturally gained, even if not actively commenting or sharing new posts. A daily login could be required for these community points to be credited. This grants awards to readers too and incentivizes readers to create an account on Reddit if they browse the website often. This concept could also be leveraged to provide some level of reputation based upon duration and consistency of contribution to a community subreddit.

Dragon Den

Dragonchain has already built a social media platform that harnesses community involvement. Dragon Den is a decentralized community built on the Dragonchain blockchain platform. Dragon Den is Dragonchain’s answer to fake news, trolling, and censorship. It incentivizes the creation and evaluation of quality content within communities. It could be described as being a shareholder of a subreddit or Reddit in its entirety. The more your subreddit is thriving, the more rewarding it will be. Den is currently in a public beta and in active development, though the real token economy is not live yet. There are different tokens for various purposes. Two tokens are Lair Ownership Rights (LOR) and Lair Ownership Tokens (LOT). LOT is a non-fungible token for ownership of a specific Lair. LOT will only be created and converted from LOR.
Energy (NRG) and Matter (MTR) work jointly. Your MTR determines how much NRG you receive in a 24-hour period. Providing quality content, or evaluating content will earn MTR.

Security. Users have full ownership & control of their points.
All community points awarded based upon any type of activity or gift, are secured and provable to all Interchain networks (currently BTC, ETH, ETC). Users are free to spend and withdraw their points as they please, depending on the features Reddit wants to bring into production.

Balances and transactions cannot be forged, manipulated, or blocked by Reddit or anyone else
Users can withdraw their balance to their ERC20 wallet, directly through Reddit. Reddit can cover the fees on their behalf, or the user covers this with a portion of their balance.

Users should own their points and be able to get on-chain ERC20 tokens without permission from anyone else
Through our console users can withdraw their ERC20 rewards. This can be achieved on Reddit too. Here is a walkthrough of our console, though this does not show the quick withdrawal functionality, a user can withdraw at any time. https://www.youtube.com/watch?v=aNlTMxnfVHw

Points should be recoverable to on-chain ERC20 tokens even if all third-parties involved go offline
If necessary, signed transactions from the Reddit system (e.g. Reddit + Subreddit) can be sent to the Ethereum smart contract for minting.

A public, third-party review attesting to the soundness of the design should be available
To our knowledge, at least two large corporations, including a top 3 accounting firm, have conducted positive reviews. These reviews have never been made public, as Dragonchain did not pay or contract for these studies to be released.

Bonus points
Public, third-party implementation review available or in progress
See above

Compatibility with HSMs & hardware wallets
For the purpose of this proposal, all tokenization would be on the Ethereum network using standard token contracts and as such, would be able to leverage all hardware wallet and Ethereum ecosystem services.

Other Considerations

Minting/distributing tokens is not performed by Reddit directly
This operation can be automated by smart contract on Ethereum. Subreddits can if desired have a role to play.

One off point burning, as well as recurring, non-interactive point burning (for subreddit memberships) should be possible and scalable
This is possible and scalable with interaction between Dragonchain Reddit system and Ethereum token contract(s).

Fully open-source solutions are strongly preferred
Dragonchain is fully open source (see section on Disney release after conclusion).

Conclusion

Whether it is today, or in the future, we would like to work together to bring secure flexibility to the highest standards. It is our hope to be considered by Ethereum, Reddit, and other integrative solutions so we may further discuss the possibilities of implementation. In our public demonstration, 256 million transactions were handled in our operational network on chain in 24 hours, for the low cost of $25K, which if run today would cost $625. Dragonchain’s interoperable foundation provides the atmosphere necessary to implement a frictionless community points system. Thank you for your consideration of our proposal. We look forward to working with the community to make something great!

Disney Releases Blockchain Platform as Open Source

The team at Disney created the Disney Private Blockchain Platform. The system was a hybrid interoperable blockchain platform for ledgering and smart contract development geared toward solving problems with blockchain adoption and usability. All objective evaluation would consider the team’s output a success. We released a list of use cases that we explored in some capacity at Disney, and our input on blockchain standardization as part of our participation in the W3C Blockchain Community Group.
https://lists.w3.org/Archives/Public/public-blockchain/2016May/0052.html

Open Source

In 2016, Roets proposed to release the platform as open source to spread the technology outside of Disney, as others within the W3C group were interested in the solutions that had been created inside of Disney.
Following a long process, step by step, the team met requirements for release. Among the requirements, the team had to:
  • Obtain VP support and approval for the release
  • Verify ownership of the software to be released
  • Verify that no proprietary content would be released
  • Convince the organization that there was a value to the open source community
  • Convince the organization that there was a value to Disney
  • Offer the plan for ongoing maintenance of the project outside of Disney
  • Itemize competing projects
  • Verify no conflict of interest
  • Preferred license
  • Change the project name to not use the name Disney, any Disney character, or any other associated IP - proposed Dragonchain - approved
  • Obtain legal approval
  • Approval from corporate, parks, and other business units
  • Approval from multiple Disney patent groups Copyright holder defined by Disney (Disney Connected and Advanced Technologies)
  • Trademark searches conducted for the selected name Dragonchain
  • Obtain IT security approval
  • Manual review of OSS components conducted
  • OWASP Dependency and Vulnerability Check Conducted
  • Obtain technical (software) approval
  • Offer management, process, and financial plans for the maintenance of the project.
  • Meet list of items to be addressed before release
  • Remove all Disney project references and scripts
  • Create a public distribution list for email communications
  • Remove Roets’ direct and internal contact information
  • Create public Slack channel and move from Disney slack channels
  • Create proper labels for issue tracking
  • Rename internal private Github repository
  • Add informative description to Github page
  • Expand README.md with more specific information
  • Add information beyond current “Blockchains are Magic”
  • Add getting started sections and info on cloning/forking the project
  • Add installation details
  • Add uninstall process
  • Add unit, functional, and integration test information
  • Detail how to contribute and get involved
  • Describe the git workflow that the project will use
  • Move to public, non-Disney git repository (Github or Bitbucket)
  • Obtain Disney Open Source Committee approval for release
On top of meeting the above criteria, as part of the process, the maintainer of the project had to receive the codebase on their own personal email and create accounts for maintenance (e.g. Github) with non-Disney accounts. Given the fact that the project spanned multiple business units, Roets was individually responsible for its ongoing maintenance. Because of this, he proposed in the open source application to create a non-profit organization to hold the IP and maintain the project. This was approved by Disney.
The Disney Open Source Committee approved the application known as OSSRELEASE-10, and the code was released on October 2, 2016. Disney decided to not issue a press release.
Original OSSRELASE-10 document

Dragonchain Foundation

The Dragonchain Foundation was created on January 17, 2017. https://den.social/l/Dragonchain/24130078352e485d96d2125082151cf0/dragonchain-and-disney/
submitted by j0j0r0 to ethereum [link] [comments]

Decentr ($DEC) - foundational cross-chain and cross-platform DeFi protocol

  1. SUMMARY
Decentr is a protocol designed to make blockchain/DLT mainstream by allowing DeFi applications built on various blockchains to “talk to each other”. Decentr is a 100% secure and decentralised Web 3.0 protocol where users can apply PDV (personal data value) to increase APR on $DEC that users loan out as part of of our DeFi dLoan features, as well as it being applied at PoS when paying for stuff online. Decentr is also building a BAT competitor browser and Chrome/Firefox extension that acts as a gateway to 100% decentralised Web 3.0
Allows DeFi Dapps to access all Decentr’s dFintech features, including dLoan, dPay. Key innovation is that the protocols is based on a user’s ability to leverage the value of their data as exchangeable “currency”.
  1. KEY CONCEPTS

  1. REVENUE MODEL
A fee is charged for every transaction using dPay whereby an exchange takes place between money (fiat and digital) and data, and vice versa, either as part of DeFi features or via a dApp built on Decentr. They are launching pilot programmes in the following industries:
  1. Banking/PSP Industry: On Product launch, due to Decentr’s powerful PSP connections (including the worlds #2 PSP by volume), a medium-scale pilot program will be launched, which will seed the network with 150,000 PSP customers in primarily the Spanish/LAC markets, generating revenue from day one.
  2. “Bricks and Mortar” Supermarket/Grocery Industry: Decentr aims to ensure the long-term competitiveness of “bricks and mortar” supermarkets against online-only grocery retailers, such as Amazon, by a) building secure tech that allows supermarkets to digitise every aspect of their supply chains and operational functions, while b) allowing supermarkets to leverage this incredibly valuable data as a liquid asset class. Expected revenue by Year 5: $114Mn per year.
  3. Online Advertising Industry: Decentr’s 100% decentralised platform credits users secure data with payable value, in the form of PDV, for engaging with ads. The Brave browser was launched in 2012 and in 8 years has reached over 12 million monthly active users, accented by as many as 4.3 million daily active users.
  4. TOKEN $DEC AND SALE
Decentr recently complete their token sale on a purchase portal powered by Dolomite where they raised $974,000 in 10 minutes for a total sale hardcap of 1.25M. The $DEC token is actively trading on multiple exchanges including Uniswap and IDEX. Listed for free on IDEX, Hotbit, Hoo, Coinw, Tidex, BKex. Listed on CoinGecko and Coinmarketcap. Listed on Delta and Blockfolio apps.
➡️ Circulating supply: 61m $DEC.
➡️ Release schedule and token distribution LINK -> NO RELEASE UNTIL 2021.
➡️Contract Address - 0x30f271C9E86D2B7d00a6376Cd96A1cFBD5F0b9b3
➡️Decimals - 18, Ticker - DEC
➡️Uniswap link: https://uniswap.info/pai0x3AEEE5bA053eF8406420DbC5801fC95eC57b0E0A
⭐️ HOW TO BUY VIDEO: https://www.youtube.com/watch?v=iloAiv2oCRc&feature=youtu.be
$DEC Token utility:
A tradeable unit of value that is both internal and external to the Decentr platform.A unit of conversion between fiat entering and exiting the Decentr ecosystem.A way to capture the value of user data and combines the activity of every participant of the platform performing payment (dPay), or lending and borrowing (dLend), i.e a way to peg PDV to tangible/actionable value.Method of payment in the Decentr ecosystem.A method to internally underwrite the “Deconomy.
  1. NOTABLE SUPPORTERS
Simon Dedic - chief of Blockfyre: https://twitter.com/scoinaldo/status/1283787644221218817?s=20https://twitter.com/scoinaldo/status/1283719917657894912?s=21
Spectre Group Pick : https://twitter.com/SPECTREGRP/status/1284761576873041920https://twitter.com/llluckyl/status/1283765481716015111?s=21
Patrons of the Moon/Lil Uzi: https://t.me/patronsofthemoon/6764
CryptoGems: https://twitter.com/cryptogems_com/status/1283719318379925506?s=09t
tehMoonwalker pick who is a TOP 5 influencer per Binance:https://twitter.com/tehMoonwalkestatus/1284123961996050432?s=20https://twitter.com/binance/status/1279049822113198080
Holochain was one of their earliest supporters and they share a deep connection (recently an AMA was conducted in their TG group): https://medium.com/@DecentrNet/decentr-holochain-ama-29d662caed03
  1. UPCOMING NEWS
--------------------------------------------
  1. RESOURCES:
Website: https://decentr.net
Telegram: https://t.me/DecentrNet
Medium: https://medium.com/@DecentrNet
Twitter: https://twitter.com/DecentrNet
Whitepaper: https://decentr.net/files/Decentr_Whitepaper_V1.4.pdf
Technical Whitepaper: https://decentr.net/files/Decentr_Technical_Whitepaper_Data_As_Economic_Currency.pdf
Recent Articles:
⚡️- https://medium.com/@DecentrNet/decentr-token-sale-metrics-and-distribution-483bb3c58d05
⚡️- https://medium.com/@DecentrNet/how-decentrs-defi-dloan-function-benefits-dec-holders-97ff64a0c105
⚡️- https://medium.com/@DecentrNet/3-vertical-revenue-streams-decentr-is-targeting-4fa1f3dd62de
⚡️- https://medium.com/@DecentrNet/brave-browser-the-good-the-bad-and-the-fundamentally-misguided-8a8593b0ff5b
⚡️- https://medium.com/@DecentrNet/how-decentrs-dfintech-replaces-swift-sct-inst-clearing-house-and-other-payment-solutions-78acacbb4c3f
Chad Gang STRONG Community: https://t.me/decentrtrading
Community News Channel: https://t.me/chadnews
Recent Uniswap trades: https://t.me/dectrades
Wallet holder tracker: https://t.me/DEC_WALLETS_COUNT
submitted by ldd999 to CryptoMoonShots [link] [comments]

Scaling Reddit Community Points with Arbitrum Rollup: a piece of cake

Scaling Reddit Community Points with Arbitrum Rollup: a piece of cake
https://preview.redd.it/b80c05tnb9e51.jpg?width=2550&format=pjpg&auto=webp&s=850282c1a3962466ed44f73886dae1c8872d0f31
Submitted for consideration to The Great Reddit Scaling Bake-Off
Baked by the pastry chefs at Offchain Labs
Please send questions or comments to [[email protected] ](mailto:[email protected])
1. Overview
We're excited to submit Arbitrum Rollup for consideration to The Great Reddit Scaling Bake-Off. Arbitrum Rollup is the only Ethereum scaling solution that supports arbitrary smart contracts without compromising on Ethereum's security or adding points of centralization. For Reddit, this means that Arbitrum can not only scale the minting and transfer of Community Points, but it can foster a creative ecosystem built around Reddit Community Points enabling points to be used in a wide variety of third party applications. That's right -- you can have your cake and eat it too!
Arbitrum Rollup isn't just Ethereum-style. Its Layer 2 transactions are byte-for-byte identical to Ethereum, which means Ethereum users can continue to use their existing addresses and wallets, and Ethereum developers can continue to use their favorite toolchains and development environments out-of-the-box with Arbitrum. Coupling Arbitrum’s tooling-compatibility with its trustless asset interoperability, Reddit not only can scale but can onboard the entire Ethereum community at no cost by giving them the same experience they already know and love (well, certainly know).
To benchmark how Arbitrum can scale Reddit Community Points, we launched the Reddit contracts on an Arbitrum Rollup chain. Since Arbitrum provides full Solidity support, we didn't have to rewrite the Reddit contracts or try to mimic their functionality using an unfamiliar paradigm. Nope, none of that. We launched the Reddit contracts unmodified on Arbitrum Rollup complete with support for minting and distributing points. Like every Arbitrum Rollup chain, the chain included a bridge interface in which users can transfer Community Points or any other asset between the L1 and L2 chains. Arbitrum Rollup chains also support dynamic contract loading, which would allow third-party developers to launch custom ecosystem apps that integrate with Community Points on the very same chain that runs the Reddit contracts.
1.1 Why Ethereum
Perhaps the most exciting benefit of distributing Community Points using a blockchain is the ability to seamlessly port points to other applications and use them in a wide variety of contexts. Applications may include simple transfers such as a restaurant that allows Redditors to spend points on drinks. Or it may include complex smart contracts -- such as placing Community Points as a wager for a multiparty game or as collateral in a financial contract.
The common denominator between all of the fun uses of Reddit points is that it needs a thriving ecosystem of both users and developers, and the Ethereum blockchain is perhaps the only smart contract platform with significant adoption today. While many Layer 1 blockchains boast lower cost or higher throughput than the Ethereum blockchain, more often than not, these attributes mask the reality of little usage, weaker security, or both.
Perhaps another platform with significant usage will rise in the future. But today, Ethereum captures the mindshare of the blockchain community, and for Community Points to provide the most utility, the Ethereum blockchain is the natural choice.
1.2 Why Arbitrum
While Ethereum's ecosystem is unmatched, the reality is that fees are high and capacity is too low to support the scale of Reddit Community Points. Enter Arbitrum. Arbitrum Rollup provides all of the ecosystem benefits of Ethereum, but with orders of magnitude more capacity and at a fraction of the cost of native Ethereum smart contracts. And most of all, we don't change the experience from users. They continue to use the same wallets, addresses, languages, and tools.
Arbitrum Rollup is not the only solution that can scale payments, but it is the only developed solution that can scale both payments and arbitrary smart contracts trustlessly, which means that third party users can build highly scalable add-on apps that can be used without withdrawing money from the Rollup chain. If you believe that Reddit users will want to use their Community Points in smart contracts--and we believe they will--then it makes the most sense to choose a single scaling solution that can support the entire ecosystem, eliminating friction for users.
We view being able to run smart contracts in the same scaling solution as fundamentally critical since if there's significant demand in running smart contracts from Reddit's ecosystem, this would be a load on Ethereum and would itself require a scaling solution. Moreover, having different scaling solutions for the minting/distribution/spending of points and for third party apps would be burdensome for users as they'd have to constantly shuffle their Points back and forth.
2. Arbitrum at a glance
Arbitrum Rollup has a unique value proposition as it offers a combination of features that no other scaling solution achieves. Here we highlight its core attributes.
Decentralized. Arbitrum Rollup is as decentralized as Ethereum. Unlike some other Layer 2 scaling projects, Arbitrum Rollup doesn't have any centralized components or centralized operators who can censor users or delay transactions. Even in non-custodial systems, centralized components provide a risk as the operators are generally incentivized to increase their profit by extracting rent from users often in ways that severely degrade user experience. Even if centralized operators are altruistic, centralized components are subject to hacking, coercion, and potential liability.
Massive Scaling. Arbitrum achieves order of magnitude scaling over Ethereum's L1 smart contracts. Our software currently supports 453 transactions-per-second for basic transactions (at 1616 Ethereum gas per tx). We have a lot of room left to optimize (e.g. aggregating signatures), and over the next several months capacity will increase significantly. As described in detail below, Arbitrum can easily support and surpass Reddit's anticipated initial load, and its capacity will continue to improve as Reddit's capacity needs grow.
Low cost. The cost of running Arbitrum Rollup is quite low compared to L1 Ethereum and other scaling solutions such as those based on zero-knowledge proofs. Layer 2 fees are low, fixed, and predictable and should not be overly burdensome for Reddit to cover. Nobody needs to use special equipment or high-end machines. Arbitrum requires validators, which is a permissionless role that can be run on any reasonable on-line machine. Although anybody can act as a validator, in order to protect against a “tragedy of the commons” and make sure reputable validators are participating, we support a notion of “invited validators” that are compensated for their costs. In general, users pay (low) fees to cover the invited validators’ costs, but we imagine that Reddit may cover this cost for its users. See more on the costs and validator options below.
Ethereum Developer Experience. Not only does Arbitrum support EVM smart contracts, but the developer experience is identical to that of L1 Ethereum contracts and fully compatible with Ethereum tooling. Developers can port existing Solidity apps or write new ones using their favorite and familiar toolchains (e.g. Truffle, Buidler). There are no new languages or coding paradigms to learn.
Ethereum wallet compatibility. Just as in Ethereum, Arbitrum users need only hold keys, but do not have to store any coin history or additional data to protect or access their funds. Since Arbitrum transactions are semantically identical to Ethereum L1 transactions, existing Ethereum users can use their existing Ethereum keys with their existing wallet software such as Metamask.
Token interoperability. Users can easily transfer their ETH, ERC-20 and ERC-721 tokens between Ethereum and the Arbitrum Rollup chain. As we explain in detail below, it is possible to mint tokens in L2 that can subsequently be withdrawn and recognized by the L1 token contract.
Fast finality. Transactions complete with the same finality time as Ethereum L1 (and it's possible to get faster finality guarantees by trading away trust assumptions; see the Arbitrum Rollup whitepaper for details).
Non-custodial. Arbitrum Rollup is a non-custodial scaling solution, so users control their funds/points and neither Reddit nor anyone else can ever access or revoke points held by users.
Censorship Resistant. Since it's completely decentralized, and the Arbitrum protocol guarantees progress trustlessly, Arbitrum Rollup is just as censorship-proof as Ethereum.
Block explorer. The Arbitrum Rollup block explorer allows users to view and analyze transactions on the Rollup chain.
Limitations
Although this is a bake-off, we're not going to sugar coat anything. Arbitrum Rollup, like any Optimistic Rollup protocol, does have one limitation, and that's the delay on withdrawals.
As for the concrete length of the delay, we've done a good deal of internal modeling and have blogged about this as well. Our current modeling suggests a 3-hour delay is sufficient (but as discussed in the linked post there is a tradeoff space between the length of the challenge period and the size of the validators’ deposit).
Note that this doesn't mean that the chain is delayed for three hours. Arbitrum Rollup supports pipelining of execution, which means that validators can keep building new states even while previous ones are “in the pipeline” for confirmation. As the challenge delays expire for each update, a new state will be confirmed (read more about this here).
So activity and progress on the chain are not delayed by the challenge period. The only thing that's delayed is the consummation of withdrawals. Recall though that any single honest validator knows immediately (at the speed of L1 finality) which state updates are correct and can guarantee that they will eventually be confirmed, so once a valid withdrawal has been requested on-chain, every honest party knows that the withdrawal will definitely happen. There's a natural place here for a liquidity market in which a validator (or someone who trusts a validator) can provide withdrawal loans for a small interest fee. This is a no-risk business for them as they know which withdrawals will be confirmed (and can force their confirmation trustlessly no matter what anyone else does) but are just waiting for on-chain finality.
3. The recipe: How Arbitrum Rollup works
For a description of the technical components of Arbitrum Rollup and how they interact to create a highly scalable protocol with a developer experience that is identical to Ethereum, please refer to the following documents:
Arbitrum Rollup Whitepaper
Arbitrum academic paper (describes a previous version of Arbitrum)
4. Developer docs and APIs
For full details about how to set up and interact with an Arbitrum Rollup chain or validator, please refer to our developer docs, which can be found at https://developer.offchainlabs.com/.
Note that the Arbitrum version described on that site is older and will soon be replaced by the version we are entering in Reddit Bake-Off, which is still undergoing internal testing before public release.
5. Who are the validators?
As with any Layer 2 protocol, advancing the protocol correctly requires at least one validator (sometimes called block producers) that is honest and available. A natural question is: who are the validators?
Recall that the validator set for an Arbitrum chain is open and permissionless; anyone can start or stop validating at will. (A useful analogy is to full nodes on an L1 chain.) But we understand that even though anyone can participate, Reddit may want to guarantee that highly reputable nodes are validating their chain. Reddit may choose to validate the chain themselves and/or hire third-party validators.To this end, we have begun building a marketplace for validator-for-hire services so that dapp developers can outsource validation services to reputable nodes with high up-time. We've announced a partnership in which Chainlink nodes will provide Arbitrum validation services, and we expect to announce more partnerships shortly with other blockchain infrastructure providers.
Although there is no requirement that validators are paid, Arbitrum’s economic model tracks validators’ costs (e.g. amount of computation and storage) and can charge small fees on user transactions, using a gas-type system, to cover those costs. Alternatively, a single party such as Reddit can agree to cover the costs of invited validators.
6. Reddit Contract Support
Since Arbitrum contracts and transactions are byte-for-byte compatible with Ethereum, supporting the Reddit contracts is as simple as launching them on an Arbitrum chain.
Minting. Arbitrum Rollup supports hybrid L1/L2 tokens which can be minted in L2 and then withdrawn onto the L1. An L1 contract at address A can make a special call to the EthBridge which deploys a "buddy contract" to the same address A on an Arbitrum chain. Since it's deployed at the same address, users can know that the L2 contract is the authorized "buddy" of the L1 contract on the Arbitrum chain.
For minting, the L1 contract is a standard ERC-20 contract which mints and burns tokens when requested by the L2 contract. It is paired with an ERC-20 contract in L2 which mints tokens based on whatever programmer provided minting facility is desired and burns tokens when they are withdrawn from the rollup chain. Given this base infrastructure, Arbitrum can support any smart contract based method for minting tokens in L2, and indeed we directly support Reddit's signature/claim based minting in L2.
Batch minting. What's better than a mint cookie? A whole batch! In addition to supporting Reddit’s current minting/claiming scheme, we built a second minting design, which we believe outperforms the signature/claim system in many scenarios.
In the current system, Reddit periodically issues signed statements to users, who then take those statements to the blockchain to claim their tokens. An alternative approach would have Reddit directly submit the list of users/amounts to the blockchain and distribute the tokens to the users without the signature/claim process.
To optimize the cost efficiency of this approach, we designed an application-specific compression scheme to minimize the size of the batch distribution list. We analyzed the data from Reddit's previous distributions and found that the data is highly compressible since token amounts are small and repeated, and addresses appear multiple times. Our function groups transactions by size, and replaces previously-seen addresses with a shorter index value. We wrote client code to compress the data, wrote a Solidity decompressing function, and integrated that function into Reddit’s contract running on Arbitrum.
When we ran the compression function on the previous Reddit distribution data, we found that we could compress batched minting data down to to 11.8 bytes per minting event (averaged over a 6-month trace of Reddit’s historical token grants)compared with roughly 174 bytes of on-chain data needed for the signature claim approach to minting (roughly 43 for an RLP-encoded null transaction + 65 for Reddit's signature + 65 for the user's signature + roughly 8 for the number of Points) .
The relative benefit of the two approaches with respect to on-chain call data cost depends on the percentage of users that will actually claim their tokens on chain. With the above figures, batch minting will be cheaper if roughly 5% of users redeem their claims. We stress that our compression scheme is not Arbitrum-specific and would be beneficial in any general-purpose smart contract platform.
8. Benchmarks and costs
In this section, we give the full costs of operating the Reddit contracts on an Arbitrum Rollup chain including the L1 gas costs for the Rollup chain, the costs of computation and storage for the L2 validators as well as the capital lockup requirements for staking.
Arbitrum Rollup is still on testnet, so we did not run mainnet benchmarks. Instead, we measured the L1 gas cost and L2 workload for Reddit operations on Arbitrum and calculated the total cost assuming current Ethereum gas prices. As noted below in detail, our measurements do not assume that Arbitrum is consuming the entire capacity of Ethereum. We will present the details of our model now, but for full transparency you can also play around with it yourself and adjust the parameters, by copying the spreadsheet found here.
Our cost model is based on measurements of Reddit’s contracts, running unmodified (except for the addition of a batch minting function) on Arbitrum Rollup on top of Ethereum.
On the distribution of transactions and frequency of assertions. Reddit's instructions specify the following minimum parameters that submissions should support:
Over a 5 day period, your scaling PoC should be able to handle:
  • 100,000 point claims (minting & distributing points)
  • 25,000 subscriptions
  • 75,000 one-off points burning
  • 100,000 transfers
We provide the full costs of operating an Arbitrum Rollup chain with this usage under the assumption that tokens are minted or granted to users in batches, but other transactions are uniformly distributed over the 5 day period. Unlike some other submissions, we do not make unrealistic assumptions that all operations can be submitted in enormous batches. We assume that batch minting is done in batches that use only a few percent on an L1 block’s gas, and that other operations come in evenly over time and are submitted in batches, with one batch every five minutes to keep latency reasonable. (Users are probably already waiting for L1 finality, which takes at least that long to achieve.)
We note that assuming that there are only 300,000 transactions that arrive uniformly over the 5 day period will make our benchmark numbers lower, but we believe that this will reflect the true cost of running the system. To see why, say that batches are submitted every five minutes (20 L1 blocks) and there's a fixed overhead of c bytes of calldata per batch, the cost of which will get amortized over all transactions executed in that batch. Assume that each individual transaction adds a marginal cost of t. Lastly assume the capacity of the scaling system is high enough that it can support all of Reddit's 300,000 transactions within a single 20-block batch (i.e. that there is more than c + 300,000*t byes of calldata available in 20 blocks).
Consider what happens if c, the per-batch overhead, is large (which it is in some systems, but not in Arbitrum). In the scenario that transactions actually arrive at the system's capacity and each batch is full, then c gets amortized over 300,000 transactions. But if we assume that the system is not running at capacity--and only receives 300,000 transactions arriving uniformly over 5 days-- then each 20-block assertion will contain about 200 transactions, and thus each transaction will pay a nontrivial cost due to c.
We are aware that other proposals presented scaling numbers assuming that 300,000 transactions arrived at maximum capacity and was executed in a single mega-transaction, but according to our estimates, for at least one such report, this led to a reported gas price that was 2-3 orders of magnitude lower than it would have been assuming uniform arrival. We make more realistic batching assumptions, and we believe Arbitrum compares well when batch sizes are realistic.
Our model. Our cost model includes several sources of cost:
  • L1 gas costs: This is the cost of posting transactions as calldata on the L1 chain, as well as the overhead associated with each batch of transactions, and the L1 cost of settling transactions in the Arbitrum protocol.
  • Validator’s staking costs: In normal operation, one validator will need to be staked. The stake is assumed to be 0.2% of the total value of the chain (which is assumed to be $1 per user who is eligible to claim points). The cost of staking is the interest that could be earned on the money if it were not staked.
  • Validator computation and storage: Every validator must do computation to track the chain’s processing of transactions, and must maintain storage to keep track of the contracts’ EVM storage. The cost of computation and storage are estimated based on measurements, with the dollar cost of resources based on Amazon Web Services pricing.
It’s clear from our modeling that the predominant cost is for L1 calldata. This will probably be true for any plausible rollup-based system.
Our model also shows that Arbitrum can scale to workloads much larger than Reddit’s nominal workload, without exhausting L1 or L2 resources. The scaling bottleneck will ultimately be calldata on the L1 chain. We believe that cost could be reduced substantially if necessary by clever encoding of data. (In our design any compression / decompression of L2 transaction calldata would be done by client software and L2 programs, never by an L1 contract.)
9. Status of Arbitrum Rollup
Arbitrum Rollup is live on Ethereum testnet. All of the code written to date including everything included in the Reddit demo is open source and permissively licensed under the Apache V2 license. The first testnet version of Arbitrum Rollup was released on testnet in February. Our current internal version, which we used to benchmark the Reddit contracts, will be released soon and will be a major upgrade.
Both the Arbitrum design as well as the implementation are heavily audited by independent third parties. The Arbitrum academic paper was published at USENIX Security, a top-tier peer-reviewed academic venue. For the Arbitrum software, we have engaged Trail of Bits for a security audit, which is currently ongoing, and we are committed to have a clean report before launching on Ethereum mainnet.
10. Reddit Universe Arbitrum Rollup Chain
The benchmarks described in this document were all measured using the latest internal build of our software. When we release the new software upgrade publicly we will launch a Reddit Universe Arbitrum Rollup chain as a public demo, which will contain the Reddit contracts as well as a Uniswap instance and a Connext Hub, demonstrating how Community Points can be integrated into third party apps. We will also allow members of the public to dynamically launch ecosystem contracts. We at Offchain Labs will cover the validating costs for the Reddit Universe public demo.
If the folks at Reddit would like to evaluate our software prior to our public demo, please email us at [email protected] and we'd be more than happy to provide early access.
11. Even more scaling: Arbitrum Sidechains
Rollups are an excellent approach to scaling, and we are excited about Arbitrum Rollup which far surpasses Reddit's scaling needs. But looking forward to Reddit's eventual goal of supporting hundreds of millions of users, there will likely come a time when Reddit needs more scaling than any Rollup protocol can provide.
While Rollups greatly reduce costs, they don't break the linear barrier. That is, all transactions have an on-chain footprint (because all calldata must be posted on-chain), albeit a far smaller one than on native Ethereum, and the L1 limitations end up being the bottleneck for capacity and cost. Since Ethereum has limited capacity, this linear use of on-chain resources means that costs will eventually increase superlinearly with traffic.
The good news is that we at Offchain Labs have a solution in our roadmap that can satisfy this extreme-scaling setting as well: Arbitrum AnyTrust Sidechains. Arbitrum Sidechains are similar to Arbitrum Rollup, but deviate in that they name a permissioned set of validators. When a chain’s validators agree off-chain, they can greatly reduce the on-chain footprint of the protocol and require almost no data to be put on-chain. When validators can't reach unanimous agreement off-chain, the protocol reverts to Arbitrum Rollup. Technically, Arbitrum Sidechains can be viewed as a hybrid between state channels and Rollup, switching back and forth as necessary, and combining the performance and cost that state channels can achieve in the optimistic case, with the robustness of Rollup in other cases. The core technical challenge is how to switch seamlessly between modes and how to guarantee that security is maintained throughout.
Arbitrum Sidechains break through this linear barrier, while still maintaining a high level of security and decentralization. Arbitrum Sidechains provide the AnyTrust guarantee, which says that as long as any one validator is honest and available (even if you don't know which one will be), the L2 chain is guaranteed to execute correctly according to its code and guaranteed to make progress. Unlike in a state channel, offchain progress does not require unanimous consent, and liveness is preserved as long as there is a single honest validator.
Note that the trust model for Arbitrum Sidechains is much stronger than for typical BFT-style chains which introduce a consensus "voting" protocols among a small permissioned group of validators. BFT-based protocols require a supermajority (more than 2/3) of validators to agree. In Arbitrum Sidechains, by contrast, all you need is a single honest validator to achieve guaranteed correctness and progress. Notice that in Arbitrum adding validators strictly increases security since the AnyTrust guarantee provides correctness as long as any one validator is honest and available. By contrast, in BFT-style protocols, adding nodes can be dangerous as a coalition of dishonest nodes can break the protocol.
Like Arbitrum Rollup, the developer and user experiences for Arbitrum Sidechains will be identical to that of Ethereum. Reddit would be able to choose a large and diverse set of validators, and all that they would need to guarantee to break through the scaling barrier is that a single one of them will remain honest.
We hope to have Arbitrum Sidechains in production in early 2021, and thus when Reddit reaches the scale that surpasses the capacity of Rollups, Arbitrum Sidechains will be waiting and ready to help.
While the idea to switch between channels and Rollup to get the best of both worlds is conceptually simple, getting the details right and making sure that the switch does not introduce any attack vectors is highly non-trivial and has been the subject of years of our research (indeed, we were working on this design for years before the term Rollup was even coined).
12. How Arbitrum compares
We include a comparison to several other categories as well as specific projects when appropriate. and explain why we believe that Arbitrum is best suited for Reddit's purposes. We focus our attention on other Ethereum projects.
Payment only Rollups. Compared to Arbitrum Rollup, ZK-Rollups and other Rollups that only support token transfers have several disadvantages:
  • As outlined throughout the proposal, we believe that the entire draw of Ethereum is in its rich smart contracts support which is simply not achievable with today's zero-knowledge proof technology. Indeed, scaling with a ZK-Rollup will add friction to the deployment of smart contracts that interact with Community Points as users will have to withdraw their coins from the ZK-Rollup and transfer them to a smart contract system (like Arbitrum). The community will be best served if Reddit builds on a platform that has built-in, frictionless smart-contract support.
  • All other Rollup protocols of which we are aware employ a centralized operator. While it's true that users retain custody of their coins, the centralized operator can often profit from censoring, reordering, or delaying transactions. A common misconception is that since they're non-custodial protocols, a centralized sequencer does not pose a risk but this is incorrect as the sequencer can wreak havoc or shake down users for side payments without directly stealing funds.
  • Sidechain type protocols can eliminate some of these issues, but they are not trustless. Instead, they require trust in some quorum of a committee, often requiring two-third of the committee to be honest, compared to rollup protocols like Arbitrum that require only a single honest party. In addition, not all sidechain type protocols have committees that are diverse, or even non-centralized, in practice.
  • Plasma-style protocols have a centralized operator and do not support general smart contracts.
13. Concluding Remarks
While it's ultimately up to the judges’ palate, we believe that Arbitrum Rollup is the bakeoff choice that Reddit kneads. We far surpass Reddit's specified workload requirement at present, have much room to optimize Arbitrum Rollup in the near term, and have a clear path to get Reddit to hundreds of millions of users. Furthermore, we are the only project that gives developers and users the identical interface as the Ethereum blockchain and is fully interoperable and tooling-compatible, and we do this all without any new trust assumptions or centralized components.
But no matter how the cookie crumbles, we're glad to have participated in this bake-off and we thank you for your consideration.
About Offchain Labs
Offchain Labs, Inc. is a venture-funded New York company that spun out of Princeton University research, and is building the Arbitrum platform to usher in the next generation of scalable, interoperable, and compatible smart contracts. Offchain Labs is backed by Pantera Capital, Compound VC, Coinbase Ventures, and others.
Leadership Team
Ed Felten
Ed Felten is Co-founder and Chief Scientist at Offchain Labs. He is on leave from Princeton University, where he is the Robert E. Kahn Professor of Computer Science and Public Affairs. From 2015 to 2017 he served at the White House as Deputy United States Chief Technology Officer and senior advisor to the President. He is an ACM Fellow and member of the National Academy of Engineering. Outside of work, he is an avid runner, cook, and L.A. Dodgers fan.
Steven Goldfeder
Steven Goldfeder is Co-founder and Chief Executive Officer at Offchain Labs. He holds a PhD from Princeton University, where he worked at the intersection of cryptography and cryptocurrencies including threshold cryptography, zero-knowledge proof systems, and post-quantum signatures. He is a co-author of Bitcoin and Cryptocurrency Technologies, the leading textbook on cryptocurrencies, and he has previously worked at Google and Microsoft Research, where he co-invented the Picnic signature algorithm. When not working, you can find Steven spending time with his family, taking a nature walk, or twisting balloons.
Harry Kalodner
Harry Kalodner is Co-founder and Chief Technology Officer at Offchain Labs where he leads the engineering team. Before the company he attended Princeton as a Ph.D candidate where his research explored economics, anonymity, and incentive compatibility of cryptocurrencies, and he also has worked at Apple. When not up at 3:00am writing code, Harry occasionally sleeps.
submitted by hkalodner to ethereum [link] [comments]

Why i’m bullish on Zilliqa (long read)

Edit: TL;DR added in the comments
 
Hey all, I've been researching coins since 2017 and have gone through 100s of them in the last 3 years. I got introduced to blockchain via Bitcoin of course, analyzed Ethereum thereafter and from that moment I have a keen interest in smart contact platforms. I’m passionate about Ethereum but I find Zilliqa to have a better risk-reward ratio. Especially because Zilliqa has found an elegant balance between being secure, decentralized and scalable in my opinion.
 
Below I post my analysis of why from all the coins I went through I’m most bullish on Zilliqa (yes I went through Tezos, EOS, NEO, VeChain, Harmony, Algorand, Cardano etc.). Note that this is not investment advice and although it's a thorough analysis there is obviously some bias involved. Looking forward to what you all think!
 
Fun fact: the name Zilliqa is a play on ‘silica’ silicon dioxide which means “Silicon for the high-throughput consensus computer.”
 
This post is divided into (i) Technology, (ii) Business & Partnerships, and (iii) Marketing & Community. I’ve tried to make the technology part readable for a broad audience. If you’ve ever tried understanding the inner workings of Bitcoin and Ethereum you should be able to grasp most parts. Otherwise, just skim through and once you are zoning out head to the next part.
 
Technology and some more:
 
Introduction
 
The technology is one of the main reasons why I’m so bullish on Zilliqa. First thing you see on their website is: “Zilliqa is a high-performance, high-security blockchain platform for enterprises and next-generation applications.” These are some bold statements.
 
Before we deep dive into the technology let’s take a step back in time first as they have quite the history. The initial research paper from which Zilliqa originated dates back to August 2016: Elastico: A Secure Sharding Protocol For Open Blockchains where Loi Luu (Kyber Network) is one of the co-authors. Other ideas that led to the development of what Zilliqa has become today are: Bitcoin-NG, collective signing CoSi, ByzCoin and Omniledger.
 
The technical white paper was made public in August 2017 and since then they have achieved everything stated in the white paper and also created their own open source intermediate level smart contract language called Scilla (functional programming language similar to OCaml) too.
 
Mainnet is live since the end of January 2019 with daily transaction rates growing continuously. About a week ago mainnet reached 5 million transactions, 500.000+ addresses in total along with 2400 nodes keeping the network decentralized and secure. Circulating supply is nearing 11 billion and currently only mining rewards are left. The maximum supply is 21 billion with annual inflation being 7.13% currently and will only decrease with time.
 
Zilliqa realized early on that the usage of public cryptocurrencies and smart contracts were increasing but decentralized, secure, and scalable alternatives were lacking in the crypto space. They proposed to apply sharding onto a public smart contract blockchain where the transaction rate increases almost linear with the increase in the amount of nodes. More nodes = higher transaction throughput and increased decentralization. Sharding comes in many forms and Zilliqa uses network-, transaction- and computational sharding. Network sharding opens up the possibility of using transaction- and computational sharding on top. Zilliqa does not use state sharding for now. We’ll come back to this later.
 
Before we continue dissecting how Zilliqa achieves such from a technological standpoint it’s good to keep in mind that a blockchain being decentralised and secure and scalable is still one of the main hurdles in allowing widespread usage of decentralised networks. In my opinion this needs to be solved first before blockchains can get to the point where they can create and add large scale value. So I invite you to read the next section to grasp the underlying fundamentals. Because after all these premises need to be true otherwise there isn’t a fundamental case to be bullish on Zilliqa, right?
 
Down the rabbit hole
 
How have they achieved this? Let’s define the basics first: key players on Zilliqa are the users and the miners. A user is anybody who uses the blockchain to transfer funds or run smart contracts. Miners are the (shard) nodes in the network who run the consensus protocol and get rewarded for their service in Zillings (ZIL). The mining network is divided into several smaller networks called shards, which is also referred to as ‘network sharding’. Miners subsequently are randomly assigned to a shard by another set of miners called DS (Directory Service) nodes. The regular shards process transactions and the outputs of these shards are eventually combined by the DS shard as they reach consensus on the final state. More on how these DS shards reach consensus (via pBFT) will be explained later on.
 
The Zilliqa network produces two types of blocks: DS blocks and Tx blocks. One DS Block consists of 100 Tx Blocks. And as previously mentioned there are two types of nodes concerned with reaching consensus: shard nodes and DS nodes. Becoming a shard node or DS node is being defined by the result of a PoW cycle (Ethash) at the beginning of the DS Block. All candidate mining nodes compete with each other and run the PoW (Proof-of-Work) cycle for 60 seconds and the submissions achieving the highest difficulty will be allowed on the network. And to put it in perspective: the average difficulty for one DS node is ~ 2 Th/s equaling 2.000.000 Mh/s or 55 thousand+ GeForce GTX 1070 / 8 GB GPUs at 35.4 Mh/s. Each DS Block 10 new DS nodes are allowed. And a shard node needs to provide around 8.53 GH/s currently (around 240 GTX 1070s). Dual mining ETH/ETC and ZIL is possible and can be done via mining software such as Phoenix and Claymore. There are pools and if you have large amounts of hashing power (Ethash) available you could mine solo.
 
The PoW cycle of 60 seconds is a peak performance and acts as an entry ticket to the network. The entry ticket is called a sybil resistance mechanism and makes it incredibly hard for adversaries to spawn lots of identities and manipulate the network with these identities. And after every 100 Tx Blocks which corresponds to roughly 1,5 hour this PoW process repeats. In between these 1,5 hour, no PoW needs to be done meaning Zilliqa’s energy consumption to keep the network secure is low. For more detailed information on how mining works click here.
Okay, hats off to you. You have made it this far. Before we go any deeper down the rabbit hole we first must understand why Zilliqa goes through all of the above technicalities and understand a bit more what a blockchain on a more fundamental level is. Because the core of Zilliqa’s consensus protocol relies on the usage of pBFT (practical Byzantine Fault Tolerance) we need to know more about state machines and their function. Navigate to Viewblock, a Zilliqa block explorer, and just come back to this article. We will use this site to navigate through a few concepts.
 
We have established that Zilliqa is a public and distributed blockchain. Meaning that everyone with an internet connection can send ZILs, trigger smart contracts, etc. and there is no central authority who fully controls the network. Zilliqa and other public and distributed blockchains (like Bitcoin and Ethereum) can also be defined as state machines.
 
Taking the liberty of paraphrasing examples and definitions given by Samuel Brooks’ medium article, he describes the definition of a blockchain (like Zilliqa) as: “A peer-to-peer, append-only datastore that uses consensus to synchronize cryptographically-secure data”.
 
Next, he states that: "blockchains are fundamentally systems for managing valid state transitions”. For some more context, I recommend reading the whole medium article to get a better grasp of the definitions and understanding of state machines. Nevertheless, let’s try to simplify and compile it into a single paragraph. Take traffic lights as an example: all its states (red, amber, and green) are predefined, all possible outcomes are known and it doesn’t matter if you encounter the traffic light today or tomorrow. It will still behave the same. Managing the states of a traffic light can be done by triggering a sensor on the road or pushing a button resulting in one traffic lights’ state going from green to red (via amber) and another light from red to green.
 
With public blockchains like Zilliqa, this isn’t so straightforward and simple. It started with block #1 almost 1,5 years ago and every 45 seconds or so a new block linked to the previous block is being added. Resulting in a chain of blocks with transactions in it that everyone can verify from block #1 to the current #647.000+ block. The state is ever changing and the states it can find itself in are infinite. And while the traffic light might work together in tandem with various other traffic lights, it’s rather insignificant comparing it to a public blockchain. Because Zilliqa consists of 2400 nodes who need to work together to achieve consensus on what the latest valid state is while some of these nodes may have latency or broadcast issues, drop offline or are deliberately trying to attack the network, etc.
 
Now go back to the Viewblock page take a look at the amount of transaction, addresses, block and DS height and then hit refresh. Obviously as expected you see new incremented values on one or all parameters. And how did the Zilliqa blockchain manage to transition from a previous valid state to the latest valid state? By using pBFT to reach consensus on the latest valid state.
 
After having obtained the entry ticket, miners execute pBFT to reach consensus on the ever-changing state of the blockchain. pBFT requires a series of network communication between nodes, and as such there is no GPU involved (but CPU). Resulting in the total energy consumed to keep the blockchain secure, decentralized and scalable being low.
 
pBFT stands for practical Byzantine Fault Tolerance and is an optimization on the Byzantine Fault Tolerant algorithm. To quote Blockonomi: “In the context of distributed systems, Byzantine Fault Tolerance is the ability of a distributed computer network to function as desired and correctly reach a sufficient consensus despite malicious components (nodes) of the system failing or propagating incorrect information to other peers.” Zilliqa is such a distributed computer network and depends on the honesty of the nodes (shard and DS) to reach consensus and to continuously update the state with the latest block. If pBFT is a new term for you I can highly recommend the Blockonomi article.
 
The idea of pBFT was introduced in 1999 - one of the authors even won a Turing award for it - and it is well researched and applied in various blockchains and distributed systems nowadays. If you want more advanced information than the Blockonomi link provides click here. And if you’re in between Blockonomi and the University of Singapore read the Zilliqa Design Story Part 2 dating from October 2017.
Quoting from the Zilliqa tech whitepaper: “pBFT relies upon a correct leader (which is randomly selected) to begin each phase and proceed when the sufficient majority exists. In case the leader is byzantine it can stall the entire consensus protocol. To address this challenge, pBFT offers a view change protocol to replace the byzantine leader with another one.”
 
pBFT can tolerate ⅓ of the nodes being dishonest (offline counts as Byzantine = dishonest) and the consensus protocol will function without stalling or hiccups. Once there are more than ⅓ of dishonest nodes but no more than ⅔ the network will be stalled and a view change will be triggered to elect a new DS leader. Only when more than ⅔ of the nodes are dishonest (66%) double-spend attacks become possible.
 
If the network stalls no transactions can be processed and one has to wait until a new honest leader has been elected. When the mainnet was just launched and in its early phases, view changes happened regularly. As of today the last stalling of the network - and view change being triggered - was at the end of October 2019.
 
Another benefit of using pBFT for consensus besides low energy is the immediate finality it provides. Once your transaction is included in a block and the block is added to the chain it’s done. Lastly, take a look at this article where three types of finality are being defined: probabilistic, absolute and economic finality. Zilliqa falls under the absolute finality (just like Tendermint for example). Although lengthy already we skipped through some of the inner workings from Zilliqa’s consensus: read the Zilliqa Design Story Part 3 and you will be close to having a complete picture on it. Enough about PoW, sybil resistance mechanism, pBFT, etc. Another thing we haven’t looked at yet is the amount of decentralization.
 
Decentralisation
 
Currently, there are four shards, each one of them consisting of 600 nodes. 1 shard with 600 so-called DS nodes (Directory Service - they need to achieve a higher difficulty than shard nodes) and 1800 shard nodes of which 250 are shard guards (centralized nodes controlled by the team). The amount of shard guards has been steadily declining from 1200 in January 2019 to 250 as of May 2020. On the Viewblock statistics, you can see that many of the nodes are being located in the US but those are only the (CPU parts of the) shard nodes who perform pBFT. There is no data from where the PoW sources are coming. And when the Zilliqa blockchain starts reaching its transaction capacity limit, a network upgrade needs to be executed to lift the current cap of maximum 2400 nodes to allow more nodes and formation of more shards which will allow to network to keep on scaling according to demand.
Besides shard nodes there are also seed nodes. The main role of seed nodes is to serve as direct access points (for end-users and clients) to the core Zilliqa network that validates transactions. Seed nodes consolidate transaction requests and forward these to the lookup nodes (another type of nodes) for distribution to the shards in the network. Seed nodes also maintain the entire transaction history and the global state of the blockchain which is needed to provide services such as block explorers. Seed nodes in the Zilliqa network are comparable to Infura on Ethereum.
 
The seed nodes were first only operated by Zilliqa themselves, exchanges and Viewblock. Operators of seed nodes like exchanges had no incentive to open them for the greater public. They were centralised at first. Decentralisation at the seed nodes level has been steadily rolled out since March 2020 ( Zilliqa Improvement Proposal 3 ). Currently the amount of seed nodes is being increased, they are public-facing and at the same time PoS is applied to incentivize seed node operators and make it possible for ZIL holders to stake and earn passive yields. Important distinction: seed nodes are not involved with consensus! That is still PoW as entry ticket and pBFT for the actual consensus.
 
5% of the block rewards are being assigned to seed nodes (from the beginning in 2019) and those are being used to pay out ZIL stakers. The 5% block rewards with an annual yield of 10.03% translate to roughly 610 MM ZILs in total that can be staked. Exchanges use the custodial variant of staking and wallets like Moonlet will use the non-custodial version (starting in Q3 2020). Staking is being done by sending ZILs to a smart contract created by Zilliqa and audited by Quantstamp.
 
With a high amount of DS; shard nodes and seed nodes becoming more decentralized too, Zilliqa qualifies for the label of decentralized in my opinion.
 
Smart contracts
 
Let me start by saying I’m not a developer and my programming skills are quite limited. So I‘m taking the ELI5 route (maybe 12) but if you are familiar with Javascript, Solidity or specifically OCaml please head straight to Scilla - read the docs to get a good initial grasp of how Zilliqa’s smart contract language Scilla works and if you ask yourself “why another programming language?” check this article. And if you want to play around with some sample contracts in an IDE click here. The faucet can be found here. And more information on architecture, dapp development and API can be found on the Developer Portal.
If you are more into listening and watching: check this recent webinar explaining Zilliqa and Scilla. Link is time-stamped so you’ll start right away with a platform introduction, roadmap 2020 and afterwards a proper Scilla introduction.
 
Generalized: programming languages can be divided into being ‘object-oriented’ or ‘functional’. Here is an ELI5 given by software development academy: * “all programs have two basic components, data – what the program knows – and behavior – what the program can do with that data. So object-oriented programming states that combining data and related behaviors in one place, is called “object”, which makes it easier to understand how a particular program works. On the other hand, functional programming argues that data and behavior are different things and should be separated to ensure their clarity.” *
 
Scilla is on the functional side and shares similarities with OCaml: OCaml is a general-purpose programming language with an emphasis on expressiveness and safety. It has an advanced type system that helps catch your mistakes without getting in your way. It's used in environments where a single mistake can cost millions and speed matters, is supported by an active community, and has a rich set of libraries and development tools. For all its power, OCaml is also pretty simple, which is one reason it's often used as a teaching language.
 
Scilla is blockchain agnostic, can be implemented onto other blockchains as well, is recognized by academics and won a so-called Distinguished Artifact Award award at the end of last year.
 
One of the reasons why the Zilliqa team decided to create their own programming language focused on preventing smart contract vulnerabilities is that adding logic on a blockchain, programming, means that you cannot afford to make mistakes. Otherwise, it could cost you. It’s all great and fun blockchains being immutable but updating your code because you found a bug isn’t the same as with a regular web application for example. And with smart contracts, it inherently involves cryptocurrencies in some form thus value.
 
Another difference with programming languages on a blockchain is gas. Every transaction you do on a smart contract platform like Zilliqa or Ethereum costs gas. With gas you basically pay for computational costs. Sending a ZIL from address A to address B costs 0.001 ZIL currently. Smart contracts are more complex, often involve various functions and require more gas (if gas is a new concept click here ).
 
So with Scilla, similar to Solidity, you need to make sure that “every function in your smart contract will run as expected without hitting gas limits. An improper resource analysis may lead to situations where funds may get stuck simply because a part of the smart contract code cannot be executed due to gas limits. Such constraints are not present in traditional software systems”. Scilla design story part 1
 
Some examples of smart contract issues you’d want to avoid are: leaking funds, ‘unexpected changes to critical state variables’ (example: someone other than you setting his or her address as the owner of the smart contract after creation) or simply killing a contract.
 
Scilla also allows for formal verification. Wikipedia to the rescue: In the context of hardware and software systems, formal verification is the act of proving or disproving the correctness of intended algorithms underlying a system with respect to a certain formal specification or property, using formal methods of mathematics.
 
Formal verification can be helpful in proving the correctness of systems such as: cryptographic protocols, combinational circuits, digital circuits with internal memory, and software expressed as source code.
 
Scilla is being developed hand-in-hand with formalization of its semantics and its embedding into the Coq proof assistant — a state-of-the art tool for mechanized proofs about properties of programs.”
 
Simply put, with Scilla and accompanying tooling developers can be mathematically sure and proof that the smart contract they’ve written does what he or she intends it to do.
 
Smart contract on a sharded environment and state sharding
 
There is one more topic I’d like to touch on: smart contract execution in a sharded environment (and what is the effect of state sharding). This is a complex topic. I’m not able to explain it any easier than what is posted here. But I will try to compress the post into something easy to digest.
 
Earlier on we have established that Zilliqa can process transactions in parallel due to network sharding. This is where the linear scalability comes from. We can define simple transactions: a transaction from address A to B (Category 1), a transaction where a user interacts with one smart contract (Category 2) and the most complex ones where triggering a transaction results in multiple smart contracts being involved (Category 3). The shards are able to process transactions on their own without interference of the other shards. With Category 1 transactions that is doable, with Category 2 transactions sometimes if that address is in the same shard as the smart contract but with Category 3 you definitely need communication between the shards. Solving that requires to make a set of communication rules the protocol needs to follow in order to process all transactions in a generalised fashion.
 
And this is where the downsides of state sharding comes in currently. All shards in Zilliqa have access to the complete state. Yes the state size (0.1 GB at the moment) grows and all of the nodes need to store it but it also means that they don’t need to shop around for information available on other shards. Requiring more communication and adding more complexity. Computer science knowledge and/or developer knowledge required links if you want to dig further: Scilla - language grammar Scilla - Foundations for Verifiable Decentralised Computations on a Blockchain Gas Accounting NUS x Zilliqa: Smart contract language workshop
 
Easier to follow links on programming Scilla https://learnscilla.com/home Ivan on Tech
 
Roadmap / Zilliqa 2.0
 
There is no strict defined roadmap but here are topics being worked on. And via the Zilliqa website there is also more information on the projects they are working on.
 
Business & Partnerships
 
It’s not only technology in which Zilliqa seems to be excelling as their ecosystem has been expanding and starting to grow rapidly. The project is on a mission to provide OpenFinance (OpFi) to the world and Singapore is the right place to be due to its progressive regulations and futuristic thinking. Singapore has taken a proactive approach towards cryptocurrencies by introducing the Payment Services Act 2019 (PS Act). Among other things, the PS Act will regulate intermediaries dealing with certain cryptocurrencies, with a particular focus on consumer protection and anti-money laundering. It will also provide a stable regulatory licensing and operating framework for cryptocurrency entities, effectively covering all crypto businesses and exchanges based in Singapore. According to PWC 82% of the surveyed executives in Singapore reported blockchain initiatives underway and 13% of them have already brought the initiatives live to the market. There is also an increasing list of organizations that are starting to provide digital payment services. Moreover, Singaporean blockchain developers Building Cities Beyond has recently created an innovation $15 million grant to encourage development on its ecosystem. This all suggests that Singapore tries to position itself as (one of) the leading blockchain hubs in the world.
 
Zilliqa seems to already take advantage of this and recently helped launch Hg Exchange on their platform, together with financial institutions PhillipCapital, PrimePartners and Fundnel. Hg Exchange, which is now approved by the Monetary Authority of Singapore (MAS), uses smart contracts to represent digital assets. Through Hg Exchange financial institutions worldwide can use Zilliqa's safe-by-design smart contracts to enable the trading of private equities. For example, think of companies such as Grab, Airbnb, SpaceX that are not available for public trading right now. Hg Exchange will allow investors to buy shares of private companies & unicorns and capture their value before an IPO. Anquan, the main company behind Zilliqa, has also recently announced that they became a partner and shareholder in TEN31 Bank, which is a fully regulated bank allowing for tokenization of assets and is aiming to bridge the gap between conventional banking and the blockchain world. If STOs, the tokenization of assets, and equity trading will continue to increase, then Zilliqa’s public blockchain would be the ideal candidate due to its strategic positioning, partnerships, regulatory compliance and the technology that is being built on top of it.
 
What is also very encouraging is their focus on banking the un(der)banked. They are launching a stablecoin basket starting with XSGD. As many of you know, stablecoins are currently mostly used for trading. However, Zilliqa is actively trying to broaden the use case of stablecoins. I recommend everybody to read this text that Amrit Kumar wrote (one of the co-founders). These stablecoins will be integrated in the traditional markets and bridge the gap between the crypto world and the traditional world. This could potentially revolutionize and legitimise the crypto space if retailers and companies will for example start to use stablecoins for payments or remittances, instead of it solely being used for trading.
 
Zilliqa also released their DeFi strategic roadmap (dating November 2019) which seems to be aligning well with their OpFi strategy. A non-custodial DEX is coming to Zilliqa made by Switcheo which allows cross-chain trading (atomic swaps) between ETH, EOS and ZIL based tokens. They also signed a Memorandum of Understanding for a (soon to be announced) USD stablecoin. And as Zilliqa is all about regulations and being compliant, I’m speculating on it to be a regulated USD stablecoin. Furthermore, XSGD is already created and visible on block explorer and XIDR (Indonesian Stablecoin) is also coming soon via StraitsX. Here also an overview of the Tech Stack for Financial Applications from September 2019. Further quoting Amrit Kumar on this:
 
There are two basic building blocks in DeFi/OpFi though: 1) stablecoins as you need a non-volatile currency to get access to this market and 2) a dex to be able to trade all these financial assets. The rest are built on top of these blocks.
 
So far, together with our partners and community, we have worked on developing these building blocks with XSGD as a stablecoin. We are working on bringing a USD-backed stablecoin as well. We will soon have a decentralised exchange developed by Switcheo. And with HGX going live, we are also venturing into the tokenization space. More to come in the future.”
 
Additionally, they also have this ZILHive initiative that injects capital into projects. There have been already 6 waves of various teams working on infrastructure, innovation and research, and they are not from ASEAN or Singapore only but global: see Grantees breakdown by country. Over 60 project teams from over 20 countries have contributed to Zilliqa's ecosystem. This includes individuals and teams developing wallets, explorers, developer toolkits, smart contract testing frameworks, dapps, etc. As some of you may know, Unstoppable Domains (UD) blew up when they launched on Zilliqa. UD aims to replace cryptocurrency addresses with a human-readable name and allows for uncensorable websites. Zilliqa will probably be the only one able to handle all these transactions onchain due to ability to scale and its resulting low fees which is why the UD team launched this on Zilliqa in the first place. Furthermore, Zilliqa also has a strong emphasis on security, compliance, and privacy, which is why they partnered with companies like Elliptic, ChainSecurity (part of PwC Switzerland), and Incognito. Their sister company Aqilliz (Zilliqa spelled backwards) focuses on revolutionizing the digital advertising space and is doing interesting things like using Zilliqa to track outdoor digital ads with companies like Foodpanda.
 
Zilliqa is listed on nearly all major exchanges, having several different fiat-gateways and recently have been added to Binance’s margin trading and futures trading with really good volume. They also have a very impressive team with good credentials and experience. They don't just have “tech people”. They have a mix of tech people, business people, marketeers, scientists, and more. Naturally, it's good to have a mix of people with different skill sets if you work in the crypto space.
 
Marketing & Community
 
Zilliqa has a very strong community. If you just follow their Twitter their engagement is much higher for a coin that has approximately 80k followers. They also have been ‘coin of the day’ by LunarCrush many times. LunarCrush tracks real-time cryptocurrency value and social data. According to their data, it seems Zilliqa has a more fundamental and deeper understanding of marketing and community engagement than almost all other coins. While almost all coins have been a bit frozen in the last months, Zilliqa seems to be on its own bull run. It was somewhere in the 100s a few months ago and is currently ranked #46 on CoinGecko. Their official Telegram also has over 20k people and is very active, and their community channel which is over 7k now is more active and larger than many other official channels. Their local communities also seem to be growing.
 
Moreover, their community started ‘Zillacracy’ together with the Zilliqa core team ( see www.zillacracy.com ). It’s a community-run initiative where people from all over the world are now helping with marketing and development on Zilliqa. Since its launch in February 2020 they have been doing a lot and will also run their own non-custodial seed node for staking. This seed node will also allow them to start generating revenue for them to become a self sustaining entity that could potentially scale up to become a decentralized company working in parallel with the Zilliqa core team. Comparing it to all the other smart contract platforms (e.g. Cardano, EOS, Tezos etc.) they don't seem to have started a similar initiative (correct me if I’m wrong though). This suggests in my opinion that these other smart contract platforms do not fully understand how to utilize the ‘power of the community’. This is something you cannot ‘buy with money’ and gives many projects in the space a disadvantage.
 
Zilliqa also released two social products called SocialPay and Zeeves. SocialPay allows users to earn ZILs while tweeting with a specific hashtag. They have recently used it in partnership with the Singapore Red Cross for a marketing campaign after their initial pilot program. It seems like a very valuable social product with a good use case. I can see a lot of traditional companies entering the space through this product, which they seem to suggest will happen. Tokenizing hashtags with smart contracts to get network effect is a very smart and innovative idea.
 
Regarding Zeeves, this is a tipping bot for Telegram. They already have 1000s of signups and they plan to keep upgrading it for more and more people to use it (e.g. they recently have added a quiz features). They also use it during AMAs to reward people in real-time. It’s a very smart approach to grow their communities and get familiar with ZIL. I can see this becoming very big on Telegram. This tool suggests, again, that the Zilliqa team has a deeper understanding of what the crypto space and community needs and is good at finding the right innovative tools to grow and scale.
 
To be honest, I haven’t covered everything (i’m also reaching the character limited haha). So many updates happening lately that it's hard to keep up, such as the International Monetary Fund mentioning Zilliqa in their report, custodial and non-custodial Staking, Binance Margin, Futures, Widget, entering the Indian market, and more. The Head of Marketing Colin Miles has also released this as an overview of what is coming next. And last but not least, Vitalik Buterin has been mentioning Zilliqa lately acknowledging Zilliqa and mentioning that both projects have a lot of room to grow. There is much more info of course and a good part of it has been served to you on a silver platter. I invite you to continue researching by yourself :-) And if you have any comments or questions please post here!
submitted by haveyouheardaboutit to CryptoCurrency [link] [comments]

Attention incoming interns! Here's a list of TIPS I WISH I KNEW starting my intern year, some things you can start working on now and some less commonly discussed but very important parts of your job

It’s that time of year and yet again I’ve seen plenty of incoming interns asking what they can do to prepare. I wrote this post to share some tips for all of the not-exactly-medical stuff I wish I knew before I started intern year and to share a few things that interns can do before they start to feel like they’re well prepared for the long white coat.
As a quick background, I was a surgery intern in the first half of the 2010s and much of this is informed by my notes and memories from that time in addition to everything I’ve learned since, particularly about professionalism both in medicine and in the business world with work I’ve done in the healthcare startup arena. I’m also not perfect and very much a work in progress myself and, outside the intern-specific items here, I try to do most of these things myself—sometimes more successfully than others.
So take what you think are good ideas here, leave what you don’t think would be useful, and if anyone else has anything to add, please feel free to chime in.
TL;DR: Intern year is hard. Here are some not-so-commonly-disucussed tips that may help.

Mindset

1. Being an effective intern is, at its core, about being responsible, effective and reliable.

Your day to day responsibilities are nearly always dominated by the need to get things done and to do so in a manner that lets your other team members focus on their own roles and responsibilities. What about learning clinical medicine? You'll learn plenty and fast. Don't worry.
When reading through these tips below, view them from an angle of “would this help me develop an effective system for making sure everything gets done and nothing falls through the cracks?”

2. For your in-the-hospital life as well as your outside-the-hospital life, remember this one thing: you will forget.

You will be busy and have responsibilities in a way you likely have never experienced before. This will naturally make the day-to-day things in life more difficult than you’re used to so developing ways to outsmart your forgetful brain will pay off.

3. You are a professional now. This is your career. You’re in it.

It’s easy to view your life as a trainee as a sort of advanced student or something in between a student and a “real doctor”. But that’s not true. View yourself as a professional building your career. Your intern year is just the first step of that career. You’re a real doctor as much as any other now.

4. One of the hardest things about being an intern or resident is dealing with feelings of isolation. It will take work to actively manage and overcome those feelings.

Imposter syndrome, feeling like you don’t know what you’re doing or that you don’t belong, feeling like you’re not the person you used to be, that you don’t have time to do all the “normal” things that other people do, thinking your co-residents or attendings think you’re dumb, feeling that you don’t have time for friends/family/hobbies, ruminating on “what if I screw this up and hurt a patient?”, or “this doesn’t matter -- the patient is going to XX or YY anyway” etc are all common feelings and they all share the same undercurrent of feeling isolated in one way or another. You need to actively work to find ways to confront and overcome these feelings or else they will control you. When they control you, you’re burned out.
It may not seem like it at first, but nearly every single tip below is geared towards avoiding feelings of isolation. Feeling like you’re not in control of your finances will make you feel isolated. Feeling like you’re losing a handle on your relationships will make you feel isolated. Feeling like you’re behind on your email and haven’t done all the little things in life you need to do will make you feel isolated. Read these tips through that lens.

What you can do before you start

1. Organize and update your contacts. Seriously.

Here are some ways it can help you maintain and grow your relationships.
  • Use the ‘Notes’ feature in your contacts for everyone important in your life and all the new people meet.
    • You will forget your friends’ kids names and ages. Every time you get a birth announcement or see a post on social media, go to your friend’s contact, edit the notes and put in the info. Then, when you reach out to your friends, ask about their kids...by name.
    • You will forget your friends’ boyfriend/girlfriend/wife/husband/partner’s name, especially if you’ve never met them or haven’t seen them for a long time. Put their name in your friends’ card with a note like “Started seeing Sam in June 2020, he/she’s a software engineer”. Someone you know gets married? Add their wedding date to their card.
    • You will forget how you knew people in your contacts. Met at a conference? Was a medical student on your heme onc service? Friend-of-a-friend you met at a wedding? Someone shares an interest you have? Make a note in their contact card. Tip: these notes are for you, not them. So if someone reminds you of an actor, or didn’t stop talking about bitcoin, make a note. It will help because you will forget.
  • Tag your contacts or add them to lists and use those tags/lists to your advantage.
    • Make lists or tags for your family, your medical school friends, your undergrad friends, your coresidents, your attendings, your medical students, the hospitals you’ll be working at, etc. Put those lists or tags to use like this:
      • You will forget to stay in touch with people important to you. Set reminders in your phone for every week / two weeks / month, etc to pull up a list (family, medical school friends, etc), pick someone on that list you haven’t chatted with in a while and text them and ask them how they’re doing. Aim to start a conversation, ask about what’s happening in their life. Texts are more personal and meaningful than liking a post on social media or sharing a meme. Initiating conversations with your friends and family will help you feel connected and will increase the likelihood they reach out to you.
      • Don’t label your medical students like “MS3 Laura” or “Sub-I Juan”, etc. Label them with their full name and treat them like the colleagues they are. Put them on a list, clear it out next year if you want, but don’t treat them as “MS3 XXX“ or “MS4 YYY”. I’m sure you remember feeling like a nameless/faceless medical student at times in school and I’m sure you didn’t love it. So don’t repeat that behavior. Add a note or two about them while you’re at it. Take enough interest in your medical students to treat them well. You never know when or how you’ll cross paths with them again.
      • If you rotate through different hospitals, you will forget which “ED” or “PACU” or “nursing station 3rd floor” numbers are which. Tag them or put them on a list. It’ll make finding them when you need them much easier.

2. Use a good note taking app and a good task manager app to help with both your in-hospital life and your outside-of-the-hospital life.

Here are some ways to use a notes app.
  • Make a note for each rotation you’re on. Add in any unstructured tips as they come up, like “Send all of Dr. X’s patients home with Y”, “Use the call room in the basement outside of the locker room, passcode 1234”, “Park in the X lot on the weekends”, “Dr. A likes to manage Z with Y”, “The case manager, NAME, usually sits at the computer behind the 2nd floor nurses station”, etc. Don't overthink them, just write them down when they come up. Review those notes the next time you rotate through because you will forget all those little things and they will help you in the future.
  • Create a master grocery list of all things you typically get at the grocery store. Share it with a roommate/partner so they can keep it updated too. That way if you ever stop to pick something up, you can review the list to make sure there’s nothing you’ll forget.
    • Make master lists for other things in your life too like “packing for a conference”, “packing for a family trip”, “Target/Wal-Mart household master list” so you can quickly review anytime something comes up so you minimize the chance of forgetting something
  • Make notes for all of the other stuff you have to manage in your life like your car, your apartment/house, your loans, etc and update them every time you work on that thing. Change your loan repayment? Add it to the note. Have to get your brakes fixed? Add to the note where you got it done, how much it cost, etc. Talk to your landlord about fixing the shower? Add it to the note. Have to call the medical board to sort something out with a license? Add it to the note.
  • I like two note apps on iOS: Bear for personal notes since it’s fast and has great tagging and Apple’s Notes app for shared notes
Pick a good task manager app and use it for all the things in your life that aren’t your day-to-day work
  • Cousin getting married and you can go to the wedding? Make tasks to ensure your time off, book your travel, buy a gift, rent a hotel room, etc. Then put all the relevant info into your note because...you will forget.
  • Pandemic is over and you get to present a poster at a conference? Make tasks to review your draft with your coauthors, print your poster, book your travel, submit your reimbursement, etc. Then put all the relevant info into a note. Otherwise, you’ll forget.
  • I like Things and have also liked OmniFocus. There is a ton of content on how to set one of these things up for productivity so review it and use it YouTube search

3. Take charge of your finances

When I was an intern, I figured all I had to do was pay my loans and not go into more debt. I wish I had done the following instead:
  1. Read these two books: The White Coat Investor and I Will Teach You To Be Rich. Both are very good and have different strengths. The WCI is directly applicable to you and will help educate you in ways medical school didn’t about your financial future. IWTYTBR is much more of a “millennial” book but it’s very good for explaining big concepts and for providing a system to set yourself up for success. They’re both easy and relatively quick reads and don’t require any financial background. WCI is fine as an e-book but IWTY has a bunch of dialog boxes that make the e-book a poor experience, get a physical new or used copy.
  2. Set up a budget. I use and swear by You Need A Budget. It’s the best money I spend every year. Their system is easy and straightforward and it doesn’t take long to get the hang of it. I can’t recommend it highly enough.

4. Update your CV now and keep it updated regularly

You will no doubt have to share your CV with someone at some point whether it’s for fellowship or a research project or any number of things. The time to work on it is not when someone says “can you share your CV?” -- that’s a recipe for omissions, typos and mistakes. The only thing you should be doing every time you share your CV is giving it a quick once-over to make sure you don’t spot any mistakes and to make sure it’s up to date
There are plenty of templates online and your training institution may even have a preferred format somewhere on their website. Your ERAS application will give you a good head start but most of your medical school CV lines will either be condensed or removed all together unless something was particularly notable. You can almost always find example CVs online from senior people in your department or institution with a quick web search -- use a few as a guide
Set a reminder / task to update your CV at regular intervals. Quarterly is good, yearly at least. Save new versions of it each time so you can refer to the old ones if you need to and name them in a way to let you know you’re always sharing the most recent version, e.g., LASTNAME_FIRST NAME_CV_2020-06. You will forget if the one marked “CV” only is the right one you want to share.

5. Subscribe to a couple of newsletters to stay up to date with the world outside of your hospital

  • For general news, your preferred newspaper probably has a daily email briefing. Otherwise, Axios AM/PM and Politico’s Playbook are both very good quick reads to stay up to date with current events.
    • Keep up with healthcare news so you know what’s going on in the healthcare system broadly
      • Axios Vitals is a great, quick daily healthcare news update
      • Politico’s Pulse and Morning eHealth are both very good and have quick facts at the beginning if you just want to skim
      • Rock Health’s Rock Weekly is a decent summary of each week in the healthcare startup and technology world
Pick a few of these and aim to get through them each day. If you can’t get through them, unsubscribe to the ones you think are least relevant to you so you never feel “behind” in staying up with the news. You can breeze through the few you pick in a few minutes here and there throughout the day -- don’t make it any harder than that to feel like you’re “up to date” on the news.

General tips for maintaining relationships

  • For any romantic relationship, do these things if you don’t already:
 1. Make a rule: no phones at the table. * Don’t put your phone on the table face-up. Don’t put your phone on the table face-down. Keep your phone off the table and set to silent. * Focus on the person in front of you and show them you care about them by paying attention to them. We all know what it feels like to be with someone more interested in their screen than in interacting with you. If you’re on call, say “sorry, I’m on call, I may have to check something here and there”, apologize if you do check it and then put your phone away. 2. Make another rule: no phones in bed * Same principle as at the table. Want to feel like two strangers just passing through life who just so happen to share the same bed? Wake up, reach for your phone and scroll through your feeds like a zombie before getting out of bed. Same idea before bed. Your phone can wait. 3. If you’re at the point where you share finances, set a regular meeting to review how you’re doing. * Ideally, this is a “red, yellow or green” meeting and should only take a few minutes. Money can be a big conflict issue for relationships and avoiding talking about money is a surefire way to eventually turn to conflict. If you have a budget and shared goals, this should be quick. * A monthly check-in is good. Create a recurring calendar event, attach the shared notes or spreadsheet document you use, add your goals for the meeting and honor the meeting when it comes around. 
  • Eat with people who are important to you, if you can.
    • There’s something about sharing a meal that’s special in human nature. Friends who are important to you? Partners? Mentors you’re looking to get to know better after you’ve had a few chats? Try to eat with them when you can. And keep your phone off the table.
    • The same idea works with your coresidents and teams in the hospital. Eat with them if you can. Eating with others builds, strengthens and maintains relationships. Keep your phone off the table if you can.
Think about it this way: who would you consider a better mentor, the person you’ve met with a few times in their office where they sit behind their desk and you in front of them while they glance at their computer screen every time it pings or the person who’s invited you to get coffee or food and they kept their phone away the whole time? Now turn that around and realize the power of the message you can send to people you care about by trying to eat with them and show them they have your full attention.

Hospital tips

1. Learn to think about tasks as a continuum from start to finish instead of as a binary 'done/not done'.

Let’s say you have to order a CT for a patient of yours.
  • Instead of marking the task as complete the second you place the order for the CT, recognize that the whole task is not just placing the order, but also knowing when your patient is going down to the scanner, when they’re back, when the CT is up in the system, when the report is up and also that you’ve looked at the CT yourself and have read the report.
  • When your senior or attending asks you, “Did patient X get their CT?”, a not-so-great answer is “Yes” or “No”. A better answer is “they’re down at the scanner now” or “the scan’s done but it hasn’t been read yet. Want to look at it?” or “Yes, it’s negative for XXX but did show YYY”.
Whatever system you eventually adopt for your day-to-day task management in the hospital, whether it’s a list or index cards or a printed signout sheet, make sure you’re tracking both when orders go in, when they’re complete, when they’re cancelled, etc. Just marking things as complete once you place the order isn’t enough.

2. Signout is taken, not given.

What I mean by this is that when you take signout, that means you’re accepting responsibility for those patients. They might be your patients, you might be cross-covering, it doesn’t matter. What matters is that when those patients are your responsibility, it’s your responsibility to get what you need to know to take care of them.
Is someone signing out to you in a hurry and not giving you what you need? Ask them for that relevant past medical history, those exam findings, and so on. It’s not enough for the person handing off to say “we’re worried about x or y”, you’ve got to follow that up with “in case of x or y, is there a plan for what the team wants me to do?”. Get the answers you need.
A lot of covering patients on call is playing defense whereas the primary team generally plays offense. But that doesn’t mean you can play defense in isolation. The last thing you want is for the primary team to feel surprised by your choices.
 * Here’s two ways for the above example to go when turning the patients you were covering back over the next day or whatever: 1. You: “For patient so-and-so, you said you were worried about x or y. Y happened.” Them: “What did you do?”. You: “Z”. Them: “Shit, my attending’s not gonna like that”. 2. You “Y happened so I did A like you said, it went fine and here’s the current status”. Them: “Great, thanks” * See the difference? 
  • Along the lines of taking responsibility for those patients, that means that if you couldn’t get the information you needed at signout then you have to go and see those patients and get the information you need yourself.
    • You’ll hear this idea said a bunch of different ways like “trust but verify”, “trust no one” and your comfort level will change over the year as you become more confident and comfortable. But always error on the side of going to see the patient and getting your own information at the start.

3. If you will be miserable without something when you’re in the hospital, bring it with you. You won’t reliably be able to find it at the hospital every time you need it.

  • Need coffee otherwise you turn into a demon? Bring it with you. You never know when you’ll get caught doing something and won’t be able to run to the cafeteria for your fix.
  • On call overnight and know you need food so you don’t go insane? Bring it with you. Here’s a hospital food rule: never rely on the hospital's ability to feed you. The hospital will let you down sooner or later, I guarantee it.
  • Know you always get cold on call? The day you forget your jacket/sweatshirt is the day you won’t be able to find a spare blanket in the hospital to save your life. Put a backup in your locker (if your hospital respects you enough to give you one).

Miscellaneous productivity, professionalism and lifestyle tips

1. Aim to “touch” everything only once

  • Example: your physical mail. You know, the stuff made of dead trees that accumulates in that box you check every once in a while. For every piece of mail you get, you should either trash it, file it, or act on it. Don’t touch it until you’re ready to do one of those things.
  • Example: your email. Either delete it, archive it, reply to it or do the thing it’s telling you to do right away. Don’t fall into the trap of using your inbox as a to-do list -- that’s a recipe to get burned. Use a task manager for your to-do list and aim to keep your inbox at zero. Realize that email’s true power is communication and use it as a communication tool and nothing else.
  • I’ll use the example of going to a wedding again as something to “touch once”. Aim to accomplish all the tasks at once or at least create tasks and reminders to complete those tasks all in one go. Respond to the RSVP, create the calendar invite with all the information from the invitation, share the calendar event with your date, book your travel, book your hotel, book your rental car, buy your gift from the registry and set a reminder to get your suit/dress cleaned a few weeks ahead, etc.

2. Lean to use your calendar as a tool

Professionals in the “real world” tend to live and die by their calendars. Some people, especially many senior people in medicine, don’t manage their own calendars. But you manage yours. With it you can:
  • Make sure all events—even small ones like dates or errands you want to run—have locations so all you have to do is click the location for directions
  • Send invites to friends / family / coworkers for anything you talk about doing that has the relevant info
  • Make reminders for yourself to prepare for upcoming events, i.e.., don’t count on seeing your parents’/spouses’/whomever’s birthday “coming up” to remind you to get a gift or send a card. Create an event two weeks before their birthday that says “Buy Mom a birthday card”, set it to repeat yearly and buy a card when it comes up, send it a few days later and don’t worry that it won’t get there in time.

3. Learn to use email well

Ever get an email from someone and feel their tone was terse, condescending or rude? Don’t be that person. Error on the side being polite and professional and writing in complete sentences without textspeak. It’s not hard — you type fast, even with your thumbs, I’m sure of it.
  • Learn to communicate effectively. Keep it short but not terse. State why you’re writing to someone, be clear if you’re asking a question, and think about it this way: “How am I making it as easy as possible for this person to understand why I’m emailing them and do what I’m asking them to do?
  • Don’t use a canned salutation like “Best, NAME” or even worse: “Best, INITIALS”. Use your salutation to continue to communicate your message and remember that politeness and professionalism extend through your signature.
    • I don’t know why “Best,” is so common in medicine but it’s meaningless, unthoughtful, inherently passive aggressive and I seriously read it as if the person writing it were signing off by saying “Go f*ck yourself,”. Same thing for “Regards,” and its ilk, any abbreviation like “vr,” or any form of cutesy quote.
    • Write your salutation fresh each time. Did you ask someone for something? Say “Thank you for your help”. Are you writing someone senior to you and want to sound somewhat formal? “Sincerely,” never goes out of style. Are you sharing information and essentially writing a memo? Use “Please let me know if you have any questions”. Your salutation is communication, treat it that way.
    • Sign with your name, not your initials. Signing with initials is a common way senior people will try to remind you they’re senior to you. If you do it, it’s like you’re trying to prove you’re a Cool Guy Big Shot too. It never comes across well -- even for those senior people. Initials are terse. Lowercase initials are even terser. Although they may look different at first glance, all initial signatures functionally come across as ‘FU’. Write your name.
      • If it’s a few rounds back and forth of email, it’s normal drop salutations and signatures and treat email more like texting. Keep using complete sentences without textspeak, though. I promise you’ll come across better that way.
    • Use the ‘signature’ feature of your email client to share your professional details and contact information
      • Your institution (not department) will hopefully have a format for this that’s standardized and includes minimal or no graphics. If it doesn't, then I feel sorry for all the inevitable IT headaches you will eventually endure at your institution since they clearly underfund and undervalue contemporary IT and professional services. It’s the wild west out there so find some good examples of clean, professional signature formats and make one for yourself.
      • Note: this signature lives below your salutation and sign off. It’s essentially the letterhead for your email that lets your recipient fill in the details you may not otherwise provide like your department, mailing address or fax number. It’s not a replacement for signing off of your communication professionally.
    • Never use bold, italics, underlines or different font sizes in your emails. They only make emails harder to read and jumble your message.
  • If you want to highlight something, put it in a numbered or bulleted list.
    • If you can’t communicate what you want with 2-3 bulleted points, then email is not the right medium to use. Do you like reading long emails? Of course you don’t. Write a memo, attach it as a PDF or shared doc and use the email to tell your recipients to review the attachment.
  • You will eventually, in some way or another, ask someone to introduce you to one of their contacts and or refer you for something. Learn how to write a good forwardable email that utilizes the double opt-in concept and how to make it easy on the person doing you the favor. Read more here, here and here.
    • While you’re at it, understand the power of using CC and BCC to communicate effectively.
  • Aim to answer all emails written directly to you within 24 hours.
    • If you can’t respond fully right away, respond briefly saying you got the note and that you’ll work on it and get back to them. Set a reminder or create a task to do or review the thing and get back to them once you’ve done it.
    • Do you hate being left on read in text? You do it in email every time you don’t respond to someone in a timely fashion. It’s better to share a quick, “I got it and I’m working on it message” then not replying until days or weeks later.

4. Don’t let someone else’s negative energy and/or anxiety transfer to you

You will frequently experience things like this in the hospital:
  • A co-resident disagrees with a management decision made at rounds and mentions that so-and-so is an idiot. So-and-so probably isn’t an idiot. Your co-resident probably isn’t an idiot either. Form your own opinions from your own experiences.
  • A nurse pages you with a tone that says “THIS IS REALLY BAD”. It might be, go and see. And on your way, stay calm and go over the steps in your head of what you’d do if it is, in fact, REALLY BAD. But don’t freak yourself out before you even get to the room. You won’t be able to make decisions with a clear head if you’re already worked up.
  • You’re a surgery intern and all your patients are normally on the med-surg floor. Every once in a while, one goes somewhere like heme-onc if the med-surg floor is full. Someone on your team says something like “great, now they’re going to screw up our patient”. Recognize that that floor isn’t full of terrible nurses and may just have less experiences with lines and drains and that the best thing you can do is go down there, talk to the nurse and say “here’s what we want to be called about” and “this thing may look bad but it usually isn’t and we don’t need to be called, here’s why”, and so on. Doing things like this will mean you get fewer calls. Fewer calls are good.
  • Your attending is having a bad day and you’re not enjoying your interactions with them. Don’t let that make you have a bad day too. Medicine is hard enough as it is, stick to your own bad days instead adopting other people’s. Then pull up your friend list, text a buddy and feel better.

5. Don’t neglect your physical health. Trying to eat well and stay active are even more important when you’re insanely busy.

The #1 thing you can do to help your waistline is cook your own food and pack your own meals. It doesn’t matter what you cook or how good of a cook you are, as long as you’re aiming to pack meals that an adult would eat, it will be healthier than takeout and cafeteria food. It’s better for portion control, you control all the ingredients and you get a sense of satisfaction for being on the ball. It’s better in every way.
I know it’s not realistic to always prep and pack your own food on the busiest of services but you should try to hit at least a percentage like 25% or 50% of your meals. There are no lost causes in your own health.
It will be hard to exercise and work out. You should still try to do it anyway. You will go long stretches without exercising at times. Don’t beat yourself up about it. Every day is a chance to do the thing you want to do so get back out there.

6. If your social profiles are private, consider doing some housekeeping and making them public.

Instead of thinking about them as a liability to be that needs to be hidden, think about them as a narrative you can control.
Nothing is private on the internet. Even your private profile. You never know who knows someone you know or what may get screenshotted and shared down the line.
It’s natural to run a web search on anyone you’re meeting for a date, interviewing with for a job, or researching in general. When you search your own name, what comes up? What do you think when you’re searching for someone and they have a private page? Do you ever click on a few links to see professional stuff from LinkedIn, and then some social pages to see what else you learn? So does everyone else.
Use your social pages to put forward a version of you that shows who you are, shows some interests true to yourself, makes you seem like a totally normal and reliable person (which is exactly what any potential date, partner, fellowship director or hiring manager is asking themselves about you) and doesn’t share enough information to let a patient show up at your door.
Medicine lags behind other industries with people still commonly hiding behind private pages. In the tech world, it’s more strange to not have a public page. A private page says more about you that you might want to hide red flags whereas a public page says “go ahead and look, you won’t find any red flags”. One is much more powerful than the other.

Closing and something to read

When you view your professional life, it’s natural to view your professional relationships as being a binary one between patient and physician. That’s certainly essential and certainly important, but as a professional you now have relationships to consider with so many more types of people: co-residents, faculty in your department, faculty in other departments, administrators, support staff, medical students, and so on.
Just as you had to learn how to work with patients, you will have to learn to work with all of the other people in your professional life. Truly effective professionals will treat all interactions importantly and give thought and consideration to each one. All these interactions and relationships will all affect your day-to-day experience, your well-being and, ultimately, your professional experience.
You will find yourself being not just responsible for your patients, but also for yourself, your career and your relationships. It takes effort to succeed in all of those areas. And even with effort, sometimes you’ll be winning in an area and losing in others. And in a few months it will be different -- that’s just life.
I want you to consider looking outside of books and resources written specifically for physicians when you’re trying to tackle these issues inside the hospital and out.
Medicine is a much-smaller-than-you-realize bubble with a long history of personality-driven examples of “that’s just the way we do it” or “that’s how we’ve always done it”. There are good books about medicine out there, to be sure, but you’ll benefit more professionally by learning from the wide world outside of hospitals since there are quite simply many more successful and accomplished people who’ve written great resources for all aspects of professional life that medicine tends to ignore.
I’d recommend you start with this book: Andy Grove’s High Output Management (a review by another Valley titan here). Andy escaped communist Hungary, taught himself English and rose to be CEO of Intel and went on to be a sage of Silicon Valley before he passed. This book is a how-to guide for how to be an effective professional in an organization (hint: you're now a professional in an organization) and if you’ve enjoyed this post at all, you’ll love this book. You may think that this book applies to ‘managers’ and ‘business’ and not medicine but you couldn’t be more wrong. Although it was probably written around the time you were born, nearly everything in this book is a lesson that directly applies to your professional life in medicine and when you start seeing it, you’ll feel like you’re in The Matrix.
Congratulations! You've worked hard to get here. Be proud of yourself, your degree, your long white coat and be the best doctor you can be.
submitted by kiteandkey to Residency [link] [comments]

TwoGap platform Windows System Control Center - Multi-Tool-Sammlung History of the Pleiadian and Anunnaki Wars - 2000BC - YouTube 36C3 - Uncover, Understand, Own - Regaining Control Over Your AMD CPU How a Rotary Engine Works - YouTube

bitcoin internals a technical guide to bitcoin Aug 17, 2020 Posted By Patricia Cornwell Publishing TEXT ID 74685fb6 Online PDF Ebook Epub Library internals a technical guide to bitcoin description proof bitcoin internals will guide you through the inner workings of the bitcoin system exposing its brilliant design and all called bitcoin internals is relatively short and only covers the highlights of key components of the protocol but it can serve as a good launching point for further exploration you can follow the references or branch out on your own as a bonus the author also doesnt dwell on the politics and. bitcoin internals a technical guide to bitcoin By James Patterson FILE ID d9469e Freemium Media ... free pdf bitcoin internals a technical guide to bitcoin uploaded by jeffrey archer bitcoin internals is relatively short and only covers the highlights of key components of the protocol but it can serve as a good launching point for further exploration you can follow the references or branch out on your own as a bonus the author bitcoin technical analysis btc eyes retreat before another ... Download Bitcoin Internals: A Technical Guide to Bitcoin PDF. Report. Browse more videos ... PDF / EPUB File Name: Bitcoin_Internals_-_Chris_Clark.pdf, Bitcoin_Internals_-_Chris_Clark.epub; PDF File Size: 784 KB; EPUB File Size: 396 KB [PDF] [EPUB] Bitcoin Internals Download. If you are still wondering how to get free PDF EPUB of book Bitcoin Internals by Chris Clark. Click on below buttons to start Download Bitcoin Internals by Chris Clark PDF EPUB without registration. This is free ...

[index] [42755] [13213] [46432] [9457] [44706] [44128] [15842] [46706] [32179] [25057]

TwoGap platform

This video is unavailable. Watch Queue Queue. Watch Queue Queue # Blockstream Sidechain Proposal: https://blockstream.com/sidechains.pdf # RSK Bitcoin Mainnet Sidechain w/ Solidity EVM https://media.rsk.co/bamboo-mainnet-... Vladimir Putin is known as a ruthless leader and master manipulator. John Oliver enlists a group of singing dancers to explain that to Donald Trump. Connect ... Microsoft announces Windows Hello, designed to make your computing experience more personal and more secure. Windows Hello introduces biometric authenticatio... Wow! Awesome Dump Truck Equipment Extreme Machines Carrying Biggest Stone Follow us on Google Plus : https://plus.google.com/u/0/113708040019413945375 Blog-s...

#