1/12 @HathorNetwork offers a unique set of features for both builders and users. Some well known ones, others not so much. Let’s look at why you might want to consider Hathor as the layer 1 solution for your project. $HTR @HTRFDT #BuildOnHathor

2/12 Easy tokenization is the obvious one. You create your own token in less than a minute, no coding required. $HTR
https://t.co/kZwv4TlmRB
3/12 As opposed to ERC tokens, your custom Hathor token is a layer 1 token. It inherits the same features and security as the native token, $HTR, effectively giving your token the same level of security as the #Bitcoin $BTC blockchain.
4/12 Hathor Network also passed their security audit by @SlowMist_Team so you can feel safe knowing that your L1 token fulfills the same security requirements as $HTR.
5/12 By configuring built-in nano contracts you will be able to add logic to your token. No coding required. Native nano contracts also mitigate the risk of bugs and security issues that comes with custom smart contracts development on other platforms. $HTR
6/12 You will be able to list your token for free on #HathorSwap, Hathor’s first DEX (beta launching Q1, public release Q2) and letting users start trading instantly. Again, no coding required. $HTR
7/12 Adding your token is plug-and-play for CEXes that have listed $HTR as well. They modify a configuration string and that’s it. No coding required.
8/12 No more skyrocketing gas fees when network traffic spikes—always predictable costs. Developer grants are coming and Hathor Labs will support you on the business, architecture and development side. $HTR
9/12 Familiar L2 infrastructure is being built on Hathor right now. Chrome extensions like the Metamask-like wallet from @htrfdt will make transitioning from #Ethereum to Hathor seamless and pain free for both users and developers. Oh, and debit card app 👀 $HTR
10/12 Hathor has no congestion issues and the implementation of side-DAGs will ensure that the network scales to support future throughput requirements from blockchain-enabled industries. Hathor mainnet currently handles 200 TPS, fully decentralized, tech potential is 2000+. $HTR
11/12 With Hathor’s ease of use and the team’s focus on delivering great user experiences with minimal development and onboarding efforts, Hathor could be the ideal host for the next generation of ICOs, and fuel mass adoption. $HTR
12/12 Finally, Hathor’s simplicity reduces risk and time to market for businesses wanting to dip their toe into the potential of product and business model tokenization. With—you guessed it—no coding required $HTR

Your turn—add the stuff I forgot, in the comments 👇🤓

More from Tech

The 12 most important pieces of information and concepts I wish I knew about equity, as a software engineer.

A thread.

1. Equity is something Big Tech and high-growth companies award to software engineers at all levels. The more senior you are, the bigger the ratio can be:


2. Vesting, cliffs, refreshers, and sign-on clawbacks.

If you get awarded equity, you'll want to understand vesting and cliffs. A 1-year cliff is pretty common in most places that award equity.

Read more in this blog post I wrote:
https://t.co/WxQ9pQh2mY


3. Stock options / ESOPs.

The most common form of equity compensation at early-stage startups that are high-growth.

And there are *so* many pitfalls you'll want to be aware of. You need to do your research on this: I can't do justice in a tweet.

https://t.co/cudLn3ngqi


4. RSUs (Restricted Stock Units)

A common form of equity compensation for publicly traded companies and Big Tech. One of the easier types of equity to understand: https://t.co/a5xU1H9IHP

5. Double-trigger RSUs. Typically RSUs for pre-IPO companies. I got these at Uber.


6. ESPP: a (typically) amazing employee perk at publicly traded companies. There's always risk, but this plan can typically offer good upsides.

7. Phantom shares. An interesting setup similar to RSUs... but you don't own stocks. Not frequent, but e.g. Adyen goes with this plan.

You May Also Like

This is a pretty valiant attempt to defend the "Feminist Glaciology" article, which says conventional wisdom is wrong, and this is a solid piece of scholarship. I'll beg to differ, because I think Jeffery, here, is confusing scholarship with "saying things that seem right".


The article is, at heart, deeply weird, even essentialist. Here, for example, is the claim that proposing climate engineering is a "man" thing. Also a "man" thing: attempting to get distance from a topic, approaching it in a disinterested fashion.


Also a "man" thing—physical courage. (I guess, not quite: physical courage "co-constitutes" masculinist glaciology along with nationalism and colonialism.)


There's criticism of a New York Times article that talks about glaciology adventures, which makes a similar point.


At the heart of this chunk is the claim that glaciology excludes women because of a narrative of scientific objectivity and physical adventure. This is a strong claim! It's not enough to say, hey, sure, sounds good. Is it true?