Chris Curran

4.8K posts

Chris Curran banner
Chris Curran

Chris Curran

@Curran2140

@AnchorWatch - Head of Operations - Providing regulated bitcoin insurance.

Earth Katılım Nisan 2021
3K Takip Edilen1.7K Takipçiler
Chris Curran retweetledi
AnchorWatch
AnchorWatch@AnchorWatch·
Bitcoin Insurance from $250K to $100M per vault. Insurance backed by Lloyd's of London. Custody enforced by Bitcoin itself. Your custody, your way.
AnchorWatch tweet media
English
1
3
9
495
Chris Curran retweetledi
BeccaAmilee
BeccaAmilee@BeccaAmilee·
We're rethinking everything about the back office at @AnchorWatch . Tools. Ways of working. Hiring and expectations. The art of the possible. Security. Security. Security. My mind is buzzing. Across my many years at Starbucks, I utilized human-centered-design for UX, I integrated 26 systems, I was certified in and facilitated kaizen..... this changes everything. What if you could just have your back office systems....... work the way you wanted them to work? What if you could remove friction every time you encounter it? For the first time in all of history? Oh boy. This has made Rob's job harder, suddenly. Suddenly he has several toddlers (including me, chief-operating-toddler, and @Curran2140 the vastly more Claude-skilled toddler) running around "building things," and then wanting to "use the things" that we built. New rules are being established. New processes, procedures and guardrails being built. Talk about building the plane while it's in the air. It requires skill, knowledge - real engineers. Move fast, but take care!
Rob Hamilton@Rob1Ham

Random thoughts I’m having as it relates to AI because it’s the topic dujor anywhere you go. A thing I’m observing in AI discourse is a divergence how engineers vs non engineers think about and use these tools. That is ok! There is no one “right way” to think about it. Inherently, engineers are ahead of the power curve because the frontier of these tools have poor UX. If you’re not willing to touch a command line, you will be using less efficient tools. Have no fear, anything the engineers are using today will be usable in some form 3 months later for everyone with a good UX. A perfect example is Claude cowork, not a full feature parity, but close enough! The application of these tools have different margins of error if you’re using it for linguistics vs code. It’s much easier to “slop cannon” (h/t @zackbshapiro) if you’re in a word document vs a code editor, because code is deterministic and is less tolerant of fluff or outright wrong statements. Engineers are familiar with code review as a concept, now non engineers need to introduce code review into documents they generate with these tools. The dopamine hits of seeing “completed” documents on a screen is intoxicating, but you need to ride that high and comprehend and edit the output. Recursively putting an output into more LLMs is not review, if anything it’ll compound the slop. In code, we’d call this tech debt. For the first time, non engineers are now incurring their own tech debt. Non engineers are having a 0 to 1 moment. A year from now, it’ll be hard to find someone who *isn’t* an engineer in some form. Previously non engineers had to plead a case to developers to make something, now non engineers who are highly motivated and have deep understanding of their needs can become junior engineers. We are already seeing this at @AnchorWatch, where @Curran2140 spent 2 days and built maybe half of a software suite we could leverage internally. Chris has never written a line of code in his life, but it’s an impressive proof of concept. As is we’d never ship it, but working with our engineering team, it can get to 100% quickly. This is a natural evolution as the roles start to blend across an org. Chris was the main person who knew the pain points of current processes, and was in a strong position to build a product requirement doc and build something that will save him weeks of work across the year. Speaking for AnchorWatch, we are SOC-2 which requires a higher duty of care for managing data. So our existing engineering team will be in the loop (maybe that changes in a year, we will see). Strong engineering teams are able to act as scaffolding to support non engineers write code that has high impact to the organization. Further, our engineers are now better able to have a deeper appreciation for how our marketing, operations, and compliance works outside of what lives in their GitHub repository today. This extends to even me. These tools are giving me more time to focus on parts of our business outside of custody infrastructure. We don’t use LLMs for our custody software. The nuances are too mission critical to outsource the execution. AI is very helpful for prototypes and battle testing product specs, I’m often finding I’ll get deeper appreciation of edge cases I had not considered when using AI for proofs of concept, but that code then goes into the garbage to be written by hand with an increased learning. A word of caution: non engineers are less likely to understand permissions management. I can almost guarantee that if you’ve been playing around with all of these tools, it’s very likely you connected a tool to resources (like email/shared drives/local file storage), and it has way more access than you realize. This is critically important to understand for security and compliance. In 90 days, we will see a whole turnover and the meta will change again. Having high agency and metacognition will be how you can compound an edge. Finally, fun shipping!

English
2
4
46
3.9K
Chris Curran retweetledi
Rob Hamilton
Rob Hamilton@Rob1Ham·
Random thoughts I’m having as it relates to AI because it’s the topic dujor anywhere you go. A thing I’m observing in AI discourse is a divergence how engineers vs non engineers think about and use these tools. That is ok! There is no one “right way” to think about it. Inherently, engineers are ahead of the power curve because the frontier of these tools have poor UX. If you’re not willing to touch a command line, you will be using less efficient tools. Have no fear, anything the engineers are using today will be usable in some form 3 months later for everyone with a good UX. A perfect example is Claude cowork, not a full feature parity, but close enough! The application of these tools have different margins of error if you’re using it for linguistics vs code. It’s much easier to “slop cannon” (h/t @zackbshapiro) if you’re in a word document vs a code editor, because code is deterministic and is less tolerant of fluff or outright wrong statements. Engineers are familiar with code review as a concept, now non engineers need to introduce code review into documents they generate with these tools. The dopamine hits of seeing “completed” documents on a screen is intoxicating, but you need to ride that high and comprehend and edit the output. Recursively putting an output into more LLMs is not review, if anything it’ll compound the slop. In code, we’d call this tech debt. For the first time, non engineers are now incurring their own tech debt. Non engineers are having a 0 to 1 moment. A year from now, it’ll be hard to find someone who *isn’t* an engineer in some form. Previously non engineers had to plead a case to developers to make something, now non engineers who are highly motivated and have deep understanding of their needs can become junior engineers. We are already seeing this at @AnchorWatch, where @Curran2140 spent 2 days and built maybe half of a software suite we could leverage internally. Chris has never written a line of code in his life, but it’s an impressive proof of concept. As is we’d never ship it, but working with our engineering team, it can get to 100% quickly. This is a natural evolution as the roles start to blend across an org. Chris was the main person who knew the pain points of current processes, and was in a strong position to build a product requirement doc and build something that will save him weeks of work across the year. Speaking for AnchorWatch, we are SOC-2 which requires a higher duty of care for managing data. So our existing engineering team will be in the loop (maybe that changes in a year, we will see). Strong engineering teams are able to act as scaffolding to support non engineers write code that has high impact to the organization. Further, our engineers are now better able to have a deeper appreciation for how our marketing, operations, and compliance works outside of what lives in their GitHub repository today. This extends to even me. These tools are giving me more time to focus on parts of our business outside of custody infrastructure. We don’t use LLMs for our custody software. The nuances are too mission critical to outsource the execution. AI is very helpful for prototypes and battle testing product specs, I’m often finding I’ll get deeper appreciation of edge cases I had not considered when using AI for proofs of concept, but that code then goes into the garbage to be written by hand with an increased learning. A word of caution: non engineers are less likely to understand permissions management. I can almost guarantee that if you’ve been playing around with all of these tools, it’s very likely you connected a tool to resources (like email/shared drives/local file storage), and it has way more access than you realize. This is critically important to understand for security and compliance. In 90 days, we will see a whole turnover and the meta will change again. Having high agency and metacognition will be how you can compound an edge. Finally, fun shipping!
English
6
4
62
6.7K
Chris Curran retweetledi
AnchorWatch
AnchorWatch@AnchorWatch·
Launching now: • Flagship 1-Key and 3-Key Vaults • Optional Lloyd's of London insurance • @COLDCARDwallet support Coming very soon: • Multi-Institution Custody Vaults • Qualified Custody Details below: anchorwatch.com/blog/your-cust…
English
2
9
18
2.6K
Chris Curran retweetledi
AnchorWatch
AnchorWatch@AnchorWatch·
What happens to your Bitcoin if you lose a key, get hit by a bus, or your house burns down with your signing devices inside? AnchorWatch has always had the answer. Today we are launching new and better ways to protect you. Your custody, your way.
AnchorWatch tweet media
English
1
8
13
1.7K
Chris Curran retweetledi
AnchorWatch
AnchorWatch@AnchorWatch·
Most companies outgrow their custody setup long before they realize it.
English
1
3
13
1.1K
Chris Curran retweetledi
AnchorWatch
AnchorWatch@AnchorWatch·
Trident Vault is the safest way to store Bitcoin. Features include: • Multiple vaults per account (individual, SD IRA, trusts, business) • Inheritance and Proof of Assets • Whitelist addresses • User roles, including view only Your Custody. Your Way.
English
1
5
11
1.2K
Chris Curran retweetledi
AnchorWatch
AnchorWatch@AnchorWatch·
Your heirs should inherit your Bitcoin, not your stress. AnchorWatch Trident Vaults have inheritance built in from the start. Read our Inheritance 101 guide to learn more about securing your Bitcoin for the next generation. canva.com/design/DAGoHfP…
English
1
3
4
389
Chris Curran retweetledi
AnchorWatch
AnchorWatch@AnchorWatch·
Multisig with timelocks solves real world problems. AnchorWatch Trident Vault is built on miniscript and uses multisig with timelocks to secure your Bitcoin. canva.com/design/DAGBY7E…
English
1
2
7
390
Chris Curran retweetledi
AnchorWatch
AnchorWatch@AnchorWatch·
Announcing something big! @COLDCARDwallet Q Giveaway @AnchorWatch will soon be supporting COLDCARD as part of our vault offering... so we're giving one away. How to enter: • Follow @AnchorWatch & @COLDCARDwallet • Repost • Reply with your favorite COLDCARD feature.
AnchorWatch tweet media
English
101
90
107
36.1K
Chris Curran retweetledi
BeccaAmilee
BeccaAmilee@BeccaAmilee·
At @anchorwatch, we've been retweeting a lot of @lopp recently... which is never a good sign. It means there's a rash of wrench attacks going on. We worked very hard to include coverage on bitcoin if stolen from a Trident Vault due to wrench attacks. But our Flagship Custody policy only covers the Bitcoin in your vault - not a ransom payment if gathered by family or colleagues from funds elsewhere; not the expenses that you would incur during a kidnapping. Aside from the financial risks... ...a violent kidnapping requires the expertise of professional hostage negotiators. That's why for the last couple of months, we have been selling Kidnap & Ransom insurance policies to individuals and companies - regardless of how or where you store your bitcoin (we don't need to know). Or even if you own bitcoin. Watch collectors and crypto bros, or anyone else who has reason to be targeted, should have K&R in place. K&R policies are unique in a few ways. 1. You can't talk about them. If you do, you'll void your policy. (Lloyd's is serious about that. Hush.) So you're not going to hear about K&R from your friends or mentors. If you're asked if you have one, you say no or avoid the question. 2. A company policy covers employees' families as well as the employees. 3. The coverage is expansive. For example, a $5M AnchorWatch K&R policy would cover a $5M ransom payment, $5M in legal fees, $5M in medical expenses, and other items. Things like mental health, lost income, funeral expenses and many other expenses are covered. For the level of coverage, K&R insurance is very well priced. Our policy covers unlimited expenses incurred using the services of world-class hostage negotiators. 4. That last part is important. K&R policies include 24/7 access to world class security professionals and hostage negotiators. Within minutes of knowing a crisis is underway, the pros are on the job, coordinating with family members or the business as well as with global law enforcement. These services aren't cheap, but you don't have to think about that - they are fully covered, regardless of the extent of the bill once they've resolved the situation. Remember... shhhh. You can't talk about your K&R. It's your private security and your only job is to survive. We built AnchorWatchto make it easier and safer to own bitcoin. We realized that safety extends beyond our vaults, and now we can protect you in more ways. DM me or the @anchorwatch account, or email us at agent@anchorwatch.com if you need to learn more.
AnchorWatch@AnchorWatch

Crypto holders are becoming prime targets for Kidnap & Ransom (K&R) attacks. Criminals aren’t hacking wallets, they’re attacking people. If you hold digital assets, Kidnap & Ransom insurance should be part of your security stack. Reach out to learn more about K&R Insurance.

English
4
6
47
6.8K
Rob Hamilton
Rob Hamilton@Rob1Ham·
Wow, the bitcoin price is down so much I just paid 20,000 Bitcoin for a coffee and sandwich. Was super smooth, great @CashApp integration!
Rob Hamilton tweet media
English
50
21
509
44.3K
cam worboys
cam worboys@camworboys·
Meet Moneybot Your Ai assistant for all your money moves.
English
22
33
358
232.8K
The Hurdle Rate Podcast
The Hurdle Rate Podcast@HurdleRatePod·
Welcome back to The Hurdle Rate Podcast. Episode 33: Credit Ratings for Digital Capital. The crew is back covering Strategy's credit rating, how this could impact the insurance industry, interest coverage ration and industry credit ratings, what it will take for Bitcoin Treasury Company credit ratings to go higher, Mike Alfred, big volumes, and more. Here's the latest with @ColeMacro, @PunterJeff, @werkman and @TimKotzman. 0:30 - Welcome Back to The Hurdle Rate 1:00 - Strategy Gets a Credit Rating 13:13 - How This Will Impact the Insurance Industry 22:20 - Interest Coverage Ratio and Industry Credit Ratings 27:53 - What Will It Take for Bitcoin Treasury Companies Credit Ratings to Go Higher? 44:38 - Mike Alfred, Big Volumes, and What It All Means 51:48 - US China Trade Deal and Other Macro Tailwinds
English
45
81
473
240.8K