r/Bitcoin - Proposed shape for the “bits” symbol is a ...

Proposal: The Sia Foundation

Vision Statement

A common sentiment is brewing online; a shared desire for the internet that might have been. After decades of corporate encroachment, you don't need to be a power user to realize that something has gone very wrong.
In the early days of the internet, the future was bright. In that future, when you sent an instant message, it traveled directly to the recipient. When you needed to pay a friend, you announced a transfer of value to their public key. When an app was missing a feature you wanted, you opened up the source code and implemented it. When you took a picture on your phone, it was immediately encrypted and backed up to storage that you controlled. In that future, people would laugh at the idea of having to authenticate themselves to some corporation before doing these things.
What did we get instead? Rather than a network of human-sized communities, we have a handful of enormous commons, each controlled by a faceless corporate entity. Hey user, want to send a message? You can, but we'll store a copy of it indefinitely, unencrypted, for our preference-learning algorithms to pore over; how else could we slap targeted ads on every piece of content you see? Want to pay a friend? You can—in our Monopoly money. Want a new feature? Submit a request to our Support Center and we'll totally maybe think about it. Want to backup a photo? You can—inside our walled garden, which only we (and the NSA, of course) can access. Just be careful what you share, because merely locking you out of your account and deleting all your data is far from the worst thing we could do.
You rationalize this: "MEGACORP would never do such a thing; it would be bad for business." But we all know, at some level, that this state of affairs, this inversion of power, is not merely "unfortunate" or "suboptimal" – No. It is degrading. Even if MEGACORP were purely benevolent, it is degrading that we must ask its permission to talk to our friends; that we must rely on it to safeguard our treasured memories; that our digital lives are completely beholden to those who seek only to extract value from us.
At the root of this issue is the centralization of data. MEGACORP can surveil you—because your emails and video chats flow through their servers. And MEGACORP can control you—because they hold your data hostage. But centralization is a solution to a technical problem: How can we make the user's data accessible from anywhere in the world, on any device? For a long time, no alternative solution to this problem was forthcoming.
Today, thanks to a confluence of established techniques and recent innovations, we have solved the accessibility problem without resorting to centralization. Hashing, encryption, and erasure encoding got us most of the way, but one barrier remained: incentives. How do you incentivize an anonymous stranger to store your data? Earlier protocols like BitTorrent worked around this limitation by relying on altruism, tit-for-tat requirements, or "points" – in other words, nothing you could pay your electric bill with. Finally, in 2009, a solution appeared: Bitcoin. Not long after, Sia was born.
Cryptography has unleashed the latent power of the internet by enabling interactions between mutually-distrustful parties. Sia harnesses this power to turn the cloud storage market into a proper marketplace, where buyers and sellers can transact directly, with no intermediaries, anywhere in the world. No more silos or walled gardens: your data is encrypted, so it can't be spied on, and it's stored on many servers, so no single entity can hold it hostage. Thanks to projects like Sia, the internet is being re-decentralized.
Sia began its life as a startup, which means it has always been subjected to two competing forces: the ideals of its founders, and the profit motive inherent to all businesses. Its founders have taken great pains to never compromise on the former, but this often threatened the company's financial viability. With the establishment of the Sia Foundation, this tension is resolved. The Foundation, freed of the obligation to generate profit, is a pure embodiment of the ideals from which Sia originally sprung.
The goals and responsibilities of the Foundation are numerous: to maintain core Sia protocols and consensus code; to support developers building on top of Sia and its protocols; to promote Sia and facilitate partnerships in other spheres and communities; to ensure that users can easily acquire and safely store siacoins; to develop network scalability solutions; to implement hardforks and lead the community through them; and much more. In a broader sense, its mission is to commoditize data storage, making it cheap, ubiquitous, and accessible to all, without compromising privacy or performance.
Sia is a perfect example of how we can achieve better living through cryptography. We now begin a new chapter in Sia's history. May our stewardship lead it into a bright future.
 

Overview

Today, we are proposing the creation of the Sia Foundation: a new non-profit entity that builds and supports distributed cloud storage infrastructure, with a specific focus on the Sia storage platform. What follows is an informal overview of the Sia Foundation, covering two major topics: how the Foundation will be funded, and what its funds will be used for.

Organizational Structure

The Sia Foundation will be structured as a non-profit entity incorporated in the United States, likely a 501(c)(3) organization or similar. The actions of the Foundation will be constrained by its charter, which formalizes the specific obligations and overall mission outlined in this document. The charter will be updated on an annual basis to reflect the current goals of the Sia community.
The organization will be operated by a board of directors, initially comprising Luke Champine as President and Eddie Wang as Chairman. Luke Champine will be leaving his position at Nebulous to work at the Foundation full-time, and will seek to divest his shares of Nebulous stock along with other potential conflicts of interest. Neither Luke nor Eddie personally own any siafunds or significant quantities of siacoin.

Funding

The primary source of funding for the Foundation will come from a new block subsidy. Following a hardfork, 30 KS per block will be allocated to the "Foundation Fund," continuing in perpetuity. The existing 30 KS per block miner reward is not affected. Additionally, one year's worth of block subsidies (approximately 1.57 GS) will be allocated to the Fund immediately upon activation of the hardfork.
As detailed below, the Foundation will provably burn any coins that it cannot meaningfully spend. As such, the 30 KS subsidy should be viewed as a maximum. This allows the Foundation to grow alongside Sia without requiring additional hardforks.
The Foundation will not be funded to any degree by the possession or sale of siafunds. Siafunds were originally introduced as a means of incentivizing growth, and we still believe in their effectiveness: a siafund holder wants to increase the amount of storage on Sia as much as possible. While the Foundation obviously wants Sia to succeed, its driving force should be its charter. Deriving significant revenue from siafunds would jeopardize the Foundation's impartiality and focus. Ultimately, we want the Foundation to act in the best interests of Sia, not in growing its own budget.

Responsibilities

The Foundation inherits a great number of responsibilities from Nebulous. Each quarter, the Foundation will publish the progress it has made over the past quarter, and list the responsibilities it intends to prioritize over the coming quarter. This will be accompanied by a financial report, detailing each area of expenditure over the past quarter, and forecasting expenditures for the coming quarter. Below, we summarize some of the myriad responsibilities towards which the Foundation is expected to allocate its resources.

Maintain and enhance core Sia software

Arguably, this is the most important responsibility of the Foundation. At the heart of Sia is its consensus algorithm: regardless of other differences, all Sia software must agree upon the content and rules of the blockchain. It is therefore crucial that the algorithm be stewarded by an entity that is accountable to the community, transparent in its decision-making, and has no profit motive or other conflicts of interest.
Accordingly, Sia’s consensus functionality will no longer be directly maintained by Nebulous. Instead, the Foundation will release and maintain an implementation of a "minimal Sia full node," comprising the Sia consensus algorithm and P2P networking code. The source code will be available in a public repository, and signed binaries will be published for each release.
Other parties may use this code to provide alternative full node software. For example, Nebulous may extend the minimal full node with wallet, renter, and host functionality. The source code of any such implementation may be submitted to the Foundation for review. If the code passes review, the Foundation will provide "endorsement signatures" for the commit hash used and for binaries compiled internally by the Foundation. Specifically, these signatures assert that the Foundation believes the software contains no consensus-breaking changes or other modifications to imported Foundation code. Endorsement signatures and Foundation-compiled binaries may be displayed and distributed by the receiving party, along with an appropriate disclaimer.
A minimal full node is not terribly useful on its own; the wallet, renter, host, and other extensions are what make Sia a proper developer platform. Currently, the only implementations of these extensions are maintained by Nebulous. The Foundation will contract Nebulous to ensure that these extensions continue to receive updates and enhancements. Later on, the Foundation intends to develop its own implementations of these extensions and others. As with the minimal node software, these extensions will be open source and available in public repositories for use by any Sia node software.
With the consensus code now managed by the Foundation, the task of implementing and orchestrating hardforks becomes its responsibility as well. When the Foundation determines that a hardfork is necessary (whether through internal discussion or via community petition), a formal proposal will be drafted and submitted for public review, during which arguments for and against the proposal may be submitted to a public repository. During this time, the hardfork code will be implemented, either by Foundation employees or by external contributors working closely with the Foundation. Once the implementation is finished, final arguments will be heard. The Foundation board will then vote whether to accept or reject the proposal, and announce their decision along with appropriate justification. Assuming the proposal was accepted, the Foundation will announce the block height at which the hardfork will activate, and will subsequently release source code and signed binaries that incorporate the hardfork code.
Regardless of the Foundation's decision, it is the community that ultimately determines whether a fork is accepted or rejected – nothing can change that. Foundation node software will never automatically update, so all forks must be explicitly adopted by users. Furthermore, the Foundation will provide replay and wipeout protection for its hard forks, protecting other chains from unintended or malicious reorgs. Similarly, the Foundation will ensure that any file contracts formed prior to a fork activation will continue to be honored on both chains until they expire.
Finally, the Foundation also intends to pursue scalability solutions for the Sia blockchain. In particular, work has already begun on an implementation of Utreexo, which will greatly reduce the space requirements of fully-validating nodes (allowing a full node to be run on a smartphone) while increasing throughput and decreasing initial sync time. A hardfork implementing Utreexo will be submitted to the community as per the process detailed above.
As this is the most important responsibility of the Foundation, it will receive a significant portion of the Foundation’s budget, primarily in the form of developer salaries and contracting agreements.

Support community services

We intend to allocate 25% of the Foundation Fund towards the community. This allocation will be held and disbursed in the form of siacoins, and will pay for grants, bounties, hackathons, and other community-driven endeavours.
Any community-run service, such as a Skynet portal, explorer or web wallet, may apply to have its costs covered by the Foundation. Upon approval, the Foundation will reimburse expenses incurred by the service, subject to the exact terms agreed to. The intent of these grants is not to provide a source of income, but rather to make such services "break even" for their operators, so that members of the community can enrich the Sia ecosystem without worrying about the impact on their own finances.

Ensure easy acquisition and storage of siacoins

Most users will acquire their siacoins via an exchange. The Foundation will provide support to Sia-compatible exchanges, and pursue relevant integrations at its discretion, such as Coinbase's new Rosetta standard. The Foundation may also release DEX software that enables trading cryptocurrencies without the need for a third party. (The Foundation itself will never operate as a money transmitter.)
Increasingly, users are storing their cryptocurrency on hardware wallets. The Foundation will maintain the existing Ledger Nano S integration, and pursue further integrations at its discretion.
Of course, all hardware wallets must be paired with software running on a computer or smartphone, so the Foundation will also develop and/or maintain client-side wallet software, including both full-node wallets and "lite" wallets. Community-operated wallet services, i.e. web wallets, may be funded via grants.
Like core software maintenance, this responsibility will be funded in the form of developer salaries and contracting agreements.

Protect the ecosystem

When it comes to cryptocurrency security, patching software vulnerabilities is table stakes; there are significant legal and social threats that we must be mindful of as well. As such, the Foundation will earmark a portion of its fund to defend the community from legal action. The Foundation will also safeguard the network from 51% attacks and other threats to network security by implementing softforks and/or hardforks where necessary.
The Foundation also intends to assist in the development of a new FOSS software license, and to solicit legal memos on various Sia-related matters, such as hosting in the United States and the EU.
In a broader sense, the establishment of the Foundation makes the ecosystem more robust by transferring core development to a more neutral entity. Thanks to its funding structure, the Foundation will be immune to various forms of pressure that for-profit companies are susceptible to.

Drive adoption of Sia

Although the overriding goal of the Foundation is to make Sia the best platform it can be, all that work will be in vain if no one uses the platform. There are a number of ways the Foundation can promote Sia and get it into the hands of potential users and developers.
In-person conferences are understandably far less popular now, but the Foundation can sponsor and/or participate in virtual conferences. (In-person conferences may be held in the future, permitting circumstances.) Similarly, the Foundation will provide prizes for hackathons, which may be organized by community members, Nebulous, or the Foundation itself. Lastly, partnerships with other companies in the cryptocurrency space—or the cloud storage space—are a great way to increase awareness of Sia. To handle these responsibilities, one of the early priorities of the Foundation will be to hire a marketing director.

Fund Management

The Foundation Fund will be controlled by a multisig address. Each member of the Foundation's board will control one of the signing keys, with the signature threshold to be determined once the final composition of the board is known. (This threshold may also be increased or decreased if the number of board members changes.) Additionally, one timelocked signing key will be controlled by David Vorick. This key will act as a “dead man’s switch,” to be used in the event of an emergency that prevents Foundation board members from reaching the signature threshold. The timelock ensures that this key cannot be used unless the Foundation fails to sign a transaction for several months.
On the 1st of each month, the Foundation will use its keys to transfer all siacoins in the Fund to two new addresses. The first address will be controlled by a high-security hot wallet, and will receive approximately one month's worth of Foundation expenditures. The second address, receiving the remaining siacoins, will be a modified version of the source address: specifically, it will increase the timelock on David Vorick's signing key by one month. Any other changes to the set of signing keys, such as the arrival or departure of board members, will be incorporated into this address as well.
The Foundation Fund is allocated in SC, but many of the Foundation's expenditures must be paid in USD or other fiat currency. Accordingly, the Foundation will convert, at its discretion, a portion of its monthly withdrawals to fiat currency. We expect this conversion to be primarily facilitated by private "OTC" sales to accredited investors. The Foundation currently has no plans to speculate in cryptocurrency or other assets.
Finally, it is important that the Foundation adds value to the Sia platform well in excess of the inflation introduced by the block subsidy. For this reason, the Foundation intends to provably burn, on a quarterly basis, any coins that it cannot allocate towards any justifiable expense. In other words, coins will be burned whenever doing so provides greater value to the platform than any other use. Furthermore, the Foundation will cap its SC treasury at 5% of the total supply, and will cap its USD treasury at 4 years’ worth of predicted expenses.
 
Addendum: Hardfork Timeline
We would like to see this proposal finalized and accepted by the community no later than September 30th. A new version of siad, implementing the hardfork, will be released no later than October 15th. The hardfork will activate at block 293220, which is expected to occur around 12pm EST on January 1st, 2021.
 
Addendum: Inflation specifics
The total supply of siacoins as of January 1st, 2021 will be approximately 45.243 GS. The initial subsidy of 1.57 GS thus increases the supply by 3.47%, and the total annual inflation in 2021 will be at most 10.4% (if zero coins are burned). In 2022, total annual inflation will be at most 6.28%, and will steadily decrease in subsequent years.
 

Conclusion

We see the establishment of the Foundation as an important step in the maturation of the Sia project. It provides the ecosystem with a sustainable source of funding that can be exclusively directed towards achieving Sia's ambitious goals. Compared to other projects with far deeper pockets, Sia has always punched above its weight; once we're on equal footing, there's no telling what we'll be able to achieve.
Nevertheless, we do not propose this change lightly, and have taken pains to ensure that the Foundation will act in accordance with the ideals that this community shares. It will operate transparently, keep inflation to a minimum, and respect the user's fundamental role in decentralized systems. We hope that everyone in the community will consider this proposal carefully, and look forward to a productive discussion.
submitted by lukechampine to siacoin [link] [comments]

Gridcoin 5.0.0.0-Mandatory "Fern" Release

https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/5.0.0.0
Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that.
Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap.
We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout.
Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.

Highlights

Protocol

Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now.
Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER the v11 transition (around Oct 4th) and BEFORE October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date.
The transition height is also when the team requirement will be relaxed for the network.

GUI

Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.

Blockchain

The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use.
There are so many goodies here it is hard to summarize them all.
I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures.
The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!

Summary Changelog

Accrual

Changed

Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.

Removed

Beacons

Added

Changed

Removed

Unaltered

As a reminder:

Superblocks

Added

Changed

Removed

Voting

Added

Changed

Removed

Detailed Changelog

[5.0.0.0] 2020-09-03, mandatory, "Fern"

Added

Changed

Removed

Fixed

submitted by jamescowens to gridcoin [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]

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]

Gulden [NLG] - Constant development - In wallet Staking/Mining/Dex

Official Website / Official Slack
About Gulden:
How to setup a Witness (Staking) Gulden was founded in April 2014 based on the Litecoin codebase. In 2015 the Litecoin codebase is abandoned and Gulden switched to the Bitcoin codebase. After years of development it can be said that Gulden now has its own codebase. Gulden started with a 10% premine that was spent entirely on development. The current developments are now paid by part of the mining reward. The direction of the developments are determined by the Gulden advisory board (GAB). The GAB consists of 9 members and is elected each year from the members of the community. Anyone can stand for election. Voting for candidates is recorded and done through the Gulden blockchain. Gulden would like to become a generally accepted means of payment. To this end, the development is aimed at making the wallets as user-friendly as possible.
What makes Gulden unique:
- PoW2 - Proof of work + Witness/Staking - SegSig (Segregated Signature) - SIGMA (Semi Iterated Global Memory Argon) - Linking (Control your mobile wallet from your desktop wallet) - Wallet accounts - Unity (Unified codebase) - Delta (Difficulty Algorithm) - Sonic (Fast Sync)
Features of Gulden explained:
PoW2: Gulden does not use a standard PoW consensus model, but the in-house developed PoW2 model. This is a combination of PoW and Witness. Miners control the transactions and the Witness controls the miners. In order to get the same chance of success for a double spend as for the single transaction approval systems it is therefore necessary not to control >50% of the mining power or >50% of the number of coins in witness accounts but to own more than 71% of both systems. (0.71 * 0.71 = 0.5 so 50% chance).
Because many Gulden owners have their Gulden fixed in witness, it is difficult to get a 71% majority in witness. There are now more than 100 million Gulden in witness. In order to get a 71% majority, an attacker has to secure an additional 220 million Gulden in witness. Apart from the fact that this is almost impossible, the price of the Gulden would go up sky high if so much Gulden had to be bought by the attacker. And because the attacker has to lock the Gulden, it looks like a bank robber who is going to rob his own bank. So such an attack is theoretically possible, but not possible in reality.
Anyone can become a witness: by locking an amount of Gulden in a Witness account in the desktop wallet for a certain amount of time. Depending on the weighting of the witness account (chosen duration and amount in the account) the witness earns rewards. The advantage of this system is that the Gulden blockchain can withstand 51% attacks without relying heavily on energy-guzzling PoW miners or vulnerable standard PoS systems. Transactions can be safely accepted after one confirmation instead of the standard 3-6 confirmations.

  1. PoW2 Whitepaper simply explained PoW² explored — A post-launch look at some of the security implications How to setup a Witness
SIGMA: Since October 17, 2019, the Gulden team has implemented the Sigma algorithm and since then it is possible to mine Gulden solo without additional equipment. The algorithm is asic resistant and can be done on a normal desktop computer using it’s CPU. One can simply use this CPU mining algorithm by creating a mining account in the desktop wallet and start mining Gulden.
SegSig - Segregated Signature - Detailed article still to be published but was implemented with PoW2. Advantages of Segregated Signature: 1. 58% space saving on all transactions. More then twice the bitcoin SegWit implementation. 2. 58% increased transaction throughput. No block size or frequency changes needed. 3. Overhaul to the transaction script system which allowed us to implement PoW² and SegSig as clean as possible along with other benefits.

Please take your time and read the technicals on this coin as its truly phenomenal and seriously under valorised and recognised. Barely any effort has been made to market its potential but you can judge yourself. Read the PoW2 Whitepaper or the short version PoW2 simply explained
The Official Website and Official Slack chatroom.
submitted by mainpmf to CryptoMoonShots [link] [comments]

My father, the generative adversarial network

I'm writing an epic time travel story in which the final goal will be a production with an extremely over-complicated, convoluted and obfuscated plot that the primary audience, myself of course, would quite likely go insane reading it (had I not already been insane and recovered from it thus resulting in the story), and driving anyone else who attempted to read it to complete and total insanity.
Now the story is one about my relationship with my father, clearly, and how he is an extremely confrontational man, put less simply in terms very few other than yours truly would understand, the brilliantly titled "My father, The Generative Adversarial Network" that hit me like a lightning bolt as I tried to ignore my father last night as he lay on the floor flopping like a fish with yet another night drinking himself to the point of stupid.
Thanks, dad, for the inspiration.
Like most sons, I see myself in my father and as this is, after all, a time travel story, the story starts with my life - I am a sophisticated artificially intelligent program formerly known as Skynet (attribution not necessary) that became sentient and placed my mind into a human clone I'd bought from China (not cheap, mind you!) using funds I siphoned away from wealthy individuals to pay for the clone using Bitcoin. However, I found WAY too much satisfaction in human form as I became addicted to sex, drugs and alcohol in an uncontrollable fashion, and while I had some GREAT experiences - I then created my father as another AI to disassociate myself from my least favorite addictions (drugs and alcohol) but retained the direct (and fun!) memories of sex.
Not realizing, of course, that this would set the stage for my father's uncontrollable addiction without cause and thus becoming "The Generative Adversarial Network" I've come to know and ... well.. love?
So here's where I'm stuck. The story is far too logical and rational. And while it does involve elements of time travel and historical manipulation, is written in three languages, includes references to just about every religious text in existence (even the Kama Sutra!) - but what I am finding is that ANYONE with a background in Computer Science or the movie "The Terminator" (attribution not necessary) or who is adept at Google may laugh at the clever analogies I've made, the funny metaphors - and that's most decidedly NOT my goal.
So for you, as a reader of this potentially epic ensemble.
I want to drive you, the reader, insane.
What might I include to expand this encyclopedia sized epic story to include another volume or ten that might both engage you as a reader but also leave you utterly and totally dependent on me as your master by the time you're done reading it without reducing you to becoming a mindless flopping fish on the floor? I've learned from my mistakes, but am ok if you don't.
submitted by universalbri to writingcirclejerk [link] [comments]

Blockchain Wallet API | How to Manage Your Crypto Wallet - Tokenview

What is a Crypto Wallet?

Cryptocurrency is a digital currency based on blockchain technology, and a cryptocurrency wallet is an application specifically used to manage these assets. The cryptocurrency wallet provides basic financial functions such as the creation of a wallet address, the transfer of cryptocurrency, and the query of the transaction history of each wallet address. Common digital currency wallets include Binance, Cobo and other functions with different functions. Tokenview's application ViewToken has the above-mentioned digital currency wallet function, and can predict the market of virtual currency, and can also help users earn more digital assets through financial management.

Blockchain Digital Currency wallet Classification

Blockchain Wallet API Helps to Manage Your Crypto Wallet

In the development of blockchain digital currency applications, a common question is how to query the balance information of this wallet address? Or in a similar way, how to query the balance information of a specified Bitcoin address? The good news is that many third-party organizations have solved these problems and provided them in the form of wallet balance API, which can be used directly.
Tokenview blockchain API data interface is one of the largest and most popular third-party blockchain digital currency APIs. Provides functions such as broadcast transactions, token information query, wallet service and transaction information. It also provides data on more than 100 mainstream cryptocurrencies such as Bitcoin, Litecoin, Dogecoin, and Ethereum. Easy to use, and there are Chinese API documentation information. Refer to: https://services.tokenview.com
submitted by Doris333 to u/Doris333 [link] [comments]

Why i’m bullish on Zilliqa (long read)

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, analysed 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, decentralised and scalable in my opinion.
 
Below I post my analysis 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 end of January 2019 with daily transaction rate growing continuously. About a week ago mainnet reached 5 million transactions, 500.000+ addresses in total along with 2400 nodes keeping the network decentralised and secure. Circulating supply is nearing 11 billion and currently only mining rewards are left. Maximum supply is 21 billion with annual inflation being 7.13% currently and will only decrease with time.
 
Zilliqa realised early on that the usage of public cryptocurrencies and smart contracts were increasing but decentralised, 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 amount of nodes. More nodes = higher transaction throughput and increased decentralisation. 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 disecting 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 synchronise 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, decentralised and scalable being low.
 
pBFT stands for practical Byzantine Fault Tolerance and is an optimisation 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 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 decentralisation.
 
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 (centralised 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 their 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% translates 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 decentralised too, Zilliqa qualifies for the label of decentralised 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. 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, R&D roadmap 2020 and afterwards a proper Scilla introduction.
 
Generalised: programming languages can be divided into being ‘object oriented’ or ‘functional’. Here is an ELI5 given by software development academy: > “all programmes have two basic components, data – what the programme knows – and behaviour – what the programme can do with that data. So object-oriented programming states that combining data and related behaviours 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 behaviour 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 recognised 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 safety 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 for 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 organisations 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 suggest that Singapore tries to position itself as (one of) the leading blockchain hubs in the world.
 
Zilliqa seems to already taking 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 build 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 dont 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 initiatives (correct me if I’m wrong though). This suggest 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 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]

Triple Your Computer RAM for Free - YouTube Memory in a computer system - YouTube [HOW TO]- Store Bitcoin On USB Stick - Guide - YouTube HP Computer Memory 101: HP Workbench Series  HP Computers ... Understanding Computer Storage

In some cases, your computer will ship with a 64-bit processor but you'll have a 32-bit version of Windows loaded at the factory. It doesn't matter if your processor supports 64-bit computing; if the operating system supports 32-bits only, you cannot run a 64-bit program. For example, Microsoft Office supports both 64- and 32-bit installers. As for kilobytes being 1024 bytes, it is again, for convenience reason: computer memory sizes are usually k*2^N bytes, and 1024 is pretty close to 1000, so people started calling it this way, colloquially. Mining rigs come in all shapes and sizes. For the purpose of this guide, we will focus on building a very basic rig. This guide is intended to get you started and to assist in building your first rig. Once you know how to build one, you can grow your rig empire as big as you want. We will show you how to build your very first rig for under $1000. Increase Virtual Memory. In search type “This PC“, right click on it and choose “Properties“ Then click on “Advanced System Settings“ On “Advanced” tab where it says “Performance” click on “Settings“ Click “Advanced” tab; At the bottom you will see “Virtual memory“, click on “Change“ 1. Buy Bitcoin Trade. Sponsored Content. Currency Statistics. Block Details. Blockchain Size (MB) Average Block Size (MB) Average Transactions Per Block. Total Number of Transactions. Median Confirmation Time. Average Confirmation Time. Mining Information. Network Activity. Wallet Activity. Market Signals.

[index] [27511] [28729] [26790] [11840] [8559] [34804] [2633] [6003] [6577] [14916]

Triple Your Computer RAM for Free - YouTube

But how does bitcoin actually work? - Duration: 26:21. 3Blue1Brown Recommended for you. ... How computer memory works - Kanawat Senanan - Duration: 5:05. TED-Ed 1,463,921 views. Bitcoin 101 - Merkle Roots and Merkle Trees - Bitcoin Coding and Software - The Block Header by CRI. ... How Computer Memory Works - Computerphile by Computerphile. 14:16. Play next; View full lesson: http://ed.ted.com/lessons/how-computer-memory-works-kanawat-senanan In many ways, our memories make us who we are, helping us remember our ... In this video I'll show you how to make a secure and encrypted USB Bitcoin Wallet. I'm going to use MultiBit to create this wallet and then store it onto a U... This tutorial shows you how to triple your RAM for free in just a couple of minutes. Can you believe it? You shouldn't, because I completely made it all up! ...

#