C

Chain Blog

blog.chain.com · Company blog · on HN since 2014

Chain, a blockchain infrastructure company, posts on Bitcoin, smart contracts, cryptography and Rust engineering from its developers.

What HN saysHN links it as the work of a Bitcoin-based enterprise blockchain company, and its Rust session-types post is cited as an example of type systems enforcing domain rules.
34HN people shared it
9linked it in comments
34stories submitted
210story points
8 years agolast shared
2014people per year2026

Most-shared posts

  1. 1
    A Letter to Jamie Dimon
    15 people · 36 points · first shared 2017 · 5 comments on HN
  2. 2
    The Math Behind Bitcoin
    3 people · 20 points · first shared 2014 · discussion on HN
  3. 3
    Introducing Sequence by Chain
    3 people · 5 points · first shared 2017 · discussion on HN
  4. 4
    Introducing Ivy: a new smart contract language
    2 people · 60 points · first shared 2017 · 13 comments on HN
  5. 5
    Bitcoin's Killer Apps
    2 people · 18 points · first shared 2014 · 1 comments on HN
  6. 6
  7. 7
  8. 8
    Open Sourcing Chain Core
    2 people · 4 points · first shared 2016 · discussion on HN
  9. 9
  10. 10
  11. 11
    Chain: Introducing Sequence
    1 people · 4 points · first shared 2017 · discussion on HN
  12. 12
    Announcing Chain Core Developer Edition
    1 people · 4 points · first shared 2016 · discussion on HN
  13. 13
    Chain Takes Citi to Production
    1 people · 3 points · first shared 2017 · discussion on HN
  14. 14
    iOS 8 Touch ID Bitcoin Wallet
    1 people · 2 points · first shared 2014 · discussion on HN
  15. 15
    Explaining Ethereum
    1 people · 2 points · first shared 2014 · discussion on HN

What HN people wrote when they linked it

lostsock · 2017-12-14
Here[0] is a great article about what a blockchain is and isn't good for for. The tldr is that blockchains make tradeoffs that are bad for most things. In fact, on almost every dimension, decentralized services are worse than their centralized counterparts: They are slower They are more expensive They are less scalable They have worse user experiences They have volatile and uncertain governance And no, this isn’t just because they are new. This won’t fundamentally change with bigger blocks, lightning networks, sharding, forks, self-amending ledgers, or any other technical solutions. That’s because there are structural trade-offs that result directly from the primary design goal of these services, beneath which all other goals must be subordinated in order for them to be relevant: decentralization. [0]https://blog.chain.com/a-letter-to-jamie-dimon-de89d417cb80
golangnews · 2017-11-02
"I can calculate the movement of stars, but not the madness of men," - Newton after he lost everything investing in the south sea bubble for a second time, just before it popped. This has gained mainstream attention and no-one knows what they’re investing in any more, there is no there there to justify the price. Consider the trajectory of chain - a bitcoin startup that has gone from being about bitcoin to about block chains to about distributed ledgers to being about distributed applications (note these last things don’t care what they’re denominated in). A founder wrote one of the best write ups of this space I’ve seen, and even he is pretty skeptical: https://blog.chain.com/a-letter-to-jamie-dimon-de89d417cb80 All it needs now is for ordinary people to get nervous and start trying to realise their gains all at once for prices to plummet once again.
brianclements · 2016-01-05
I guess I can't say for sure independent of the articles I've found which say such at best, and are vague at worst, but it seems the company they are partnering with, Chain[1] is pretty committed to building on top of bitcoin's blockchain.[2] [1] http://chain.com/ [2] http://blog.chain.com/post/99177371581/bitcoins-killer-apps
ExactoKnight · 2017-08-01
The block chain offers the following unique benefits for asset transfer: - Assets move directly between entities — transfer and settlement are one-and-the-same — eliminating counterparty risk (https://en.wikipedia.org/wiki/Credit_risk#Counterparty_risk) - Assets move instantly, and settlement time is ~10 minutes (settlement can also be instant if the parties trust the other won’t “double spend”) - The transfer mechanism is public infrastructure and is always improving — everyone has a shared incentive to make it better, similar to Internet protocols like email and http - Assets and end-user data are privately controlled, and strong security for assets can be achieved by using multiple signing keys across several parties - Policy rules about the movement of assets can be enforced programmatically — whether those are “terms and conditions” or regulatory requirements - Assets are fungible and play nice together — e.g., you can use reward points to buy mobile minutes - A single transaction can include multiple entities and assets, on both sides of the transaction — e.g., you could execute a merger of two companies in a single transaction, with the inputs to the transaction being all stockholders across all share classes for both companies, and the outputs being all the newco shares going to all the new stockholders (again, no escrow service needed) - Every transaction is added to an immutable record which, while anonymous, can be used to construct a perfect audit trail…
oleganza · 2018-11-26
If your type system is powerful enough (like in Rust), then you can use it to express relations in your problem domain and have compiler enforce them for you before the code even runs. Example: https://blog.chain.com/bulletproof-multi-party-computation-in-rust-wit…
still_grokking · 2017-07-04
Ethereum is a flawed design, no question. But how does kadena's Pact compare to Ivy[1] by Chain[2]? The goals seams quite similar. [1] https://blog.chain.com/announcing-ivy-playground-395364675d0a [2] https://chain.com/
chanfest22 · 2017-10-20
I think you make some very valid points. To be clear my view isn't that blockchain is going to make banks obsolete (this blog post sums that up pretty well: https://blog.chain.com/a-letter-to-jamie-dimon-de89d417cb80). For example, certain activities that you mention, like M&A, are not going to be easily improved by just introducing a blockchain. What a blockchain is useful for is eliminating the need for a centralized, trusted third party. Where I could see this being very helpful, and a potentially disruptive force is in areas like IPOs, mitigating counterparty risk, reducing conflict of interests, etc. For example, if companies can raise capital and create liquidity for themselves with ICOs, the demand for IPOs will decrease. If investment banks break the "Chinese" wall and engage in market manipulation, then having public companies put their accounting on a public ledger will reduce the dependence on quarterly earnings reports. If more players are able to access the financial systems because they are on public ledgers rather than private ones, it will make it harder to banks to engage in oligopolistic behavior. None of these things are guaranteed to happen, and certainly they won't all happen overnight. I do see though, the potential for these types of changes to slowly chip away at some of the revenue streams that banks have enjoyed for a long time.
kanzure · 2017-07-30
Strange to not cite the origin of the confidential transactions scheme. an early writeup: https://people.xiph.org/~greg/confidential_values.txt http://diyhpl.us/wiki/transcripts/gmaxwell-confidential-transactions/ which is a transcript of https://www.youtube.com/watch?v=LHPYNZ8i1cU The actual borromean ring signature paper (compiled into pdf): http://diyhpl.us/~bryan/papers2/bitcoin/Borromean%20ring%20signatures.… Confidential transactions was later extended to confidential assets: https://blockstream.com/bitcoin17-final41.pdf and https://blog.chain.com/hidden-in-plain-sight-transacting-privately-on-…

Keyboard shortcuts

/Search
j kNext / previous blog
EnterOpen selected blog
vVisit the blog site
fFollow / unfollow
lSwitch grid / list view
dSwitch dark mode
g hHome
g pTop posts
g tTopics
g fFollowing
g lLiked
g yHistory
g qFAQ
EscBack / close