Ethan Tuttle

professional ehash shill
shill pioneer

Public Key

npub1tmycvul7aj4fxhypg5qkjgsjtx30zvnrfeufrgx9xlwtv0hne7cs67el78

NIP-05 Address

Profile Code

nprofile1qqs9ajvxw0lwe25ntjq52qtfygf9ngh3xf35u7y35rzn0h9k8meulvgpr9mhxue69uhkummnw3ezu7n9vfjkget99e3kcmm4vsq3wamnwvaz7tmjv4kxz7fwvd6hyun9de6zuenedyqs7amnwvaz7tmwdaehgu3wd4hk6qgdwaehxw309ahx7uewd3hkcqghwaehxw309aex2mrp0yh8qmr9vfehgu3wvdhk6qguwaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skcqrs30q

Publishing to

nostr.bitcoiner.social

Author Public Key

npub1tmycvul7aj4fxhypg5qkjgsjtx30zvnrfeufrgx9xlwtv0hne7cs67el78

Show more details

Last Notes

2025-11-22 04:25:29 UTC

https://video.nostr.build/ae95445b23eefe28d2fff04e5c577b8ec6f98e327ec9c9e65efac60c71cafcb9.webm

2025-11-22 00:14:24 UTC

https://video.nostr.build/7efb1f23b85f1f4b6dd59170a99f5363b51804b0a1498e4aa8027ff61d29ba53.mp4
#nevent1q…s4j0

2025-11-08 04:37:23 UTC

Ehash is going to be awesome.

2025-11-08 04:36:34 UTC

- reply

We don't need DNS where we're going.

2025-10-28 02:28:52 UTC

- reply

No. But i can help others fix mining. Maybe

2025-10-28 01:09:00 UTC

- reply

Excuse me?

2025-10-28 01:08:31 UTC

- reply

Calm down, sir. The course is clear.

2025-10-28 01:07:52 UTC

Been cooking with gas lately. Talk more soon.

2025-07-22 02:22:59 UTC

https://github.com/derekross/plektos/pull/1
@nprofile…q7kw is my homie. 🤝

2025-07-22 02:22:34 UTC

- reply

BTW. I did.
#nevent1q…25zq

2025-05-30 00:49:43 UTC

Version rolling masks and notify

2025-05-30 00:48:56 UTC

- reply

Wut?

2025-05-08 11:49:02 UTC

btc++ is banger.
eHash demo today.
1845UTC

2025-04-16 23:43:19 UTC

- reply

Duh.
#nevent1q…u3d6

2025-04-12 19:39:59 UTC

Wonder if I could vibe code CTV and CSFS activation on testnet4? 🤔

2025-02-11 01:54:50 UTC

Notedeck contributor. ✅

2025-02-09 02:54:26 UTC

- reply

@nprofile…9nh0

2025-02-09 02:52:03 UTC

Made a PR to #notedeck so you can use Ctrl+Enter to "Post now" when typing out a banger note.

2025-02-07 02:21:57 UTC

Pushed a commit to https://GitHub.com/EthnTuttle/eHash
One message type ported. SetupConnectionMint.
@nprofile…282l has made a ton of progress but it's all a fork of SRI. That repo will be much to clunky to maintain a fork of. Hashpools will need their own repo. I plan to diff the hashpools to SRI and see what data types he's added. Extract those out into their own crate. Then circle back to make a binary consuming the eHash crate and Sv2 crates.
This structure was inspired by demand pool's open sourge.

2025-02-06 02:54:18 UTC

- reply

Possible roadmap to MVP for #ecash mining pool for #bitaxes
Thoughts?
https://github.com/vnprc/hashpool/issues/1
#nevent1q…zvax

2025-02-04 00:38:01 UTC

Officially a NIP contributor

2025-01-31 14:10:11 UTC

#ecash is blinded cryptographic attestation

2025-01-31 02:31:36 UTC

- reply

@nprofile…xnfk @nprofile…282l

2025-01-31 02:30:26 UTC

#eHash
subsidize your friends, not the pools.
https://github.com/vnprc/hashpool

2025-01-29 22:41:13 UTC

Bitcoin Park is amazing. Always so amazed with the amazing people I meet here.

2025-01-03 01:45:10 UTC

- reply

That's my grandma.

2025-01-01 11:24:43 UTC

- reply

Will do!

2025-01-01 11:24:31 UTC

Happy New Year!

2024-10-27 16:44:33 UTC

- reply

Let's sign some shares. 🔥🔥
#nevent1q…7fjj

2024-10-27 16:43:24 UTC

- reply

Stop following so many thirst traps.

2024-10-15 01:04:30 UTC

- reply

#Amethyst does

2024-10-14 15:19:18 UTC

- reply

Very cool

2024-05-31 14:20:28 UTC

My write up on how #cashu #ecash like shares might he used for a #mining pool.
https://delvingbitcoin.org/t/ecash-tides-using-cashu-and-stratum-v2/870/20
#Ecash TIDES using #Cashu and #StratumV2
Recommended reading/References:
- Cashu ecash protocol
- ecash Proof of Liabilities
- Ocean TIDES
- Stratum v2 Spec (Sv2)
Goals:
- Auditability
- Small payouts
- Privacy
Using the Blind Diffie-Hellmann key exchange (BDHKE) from Cashu as a Sv2 Protocol Extension, a pool can provide auditable, small scale, private pool rewards in the form of eHash.
A hash provider (HP) connects to a pool and begins job negotiation. This aspect remains largely unchanged from current paradigms. However, the HP will also request the active block_keyset. This is a list of pubkeys as defined in NUT02, but the value amounts for the individual keys correspond to difficulty targets for various miners which is used as a share weight in the TIDES rewards. The unit for these keysets is left up to specific implementations. A block_keyset is rotated once the pool finds a block or when the network difficulty adjustment occurs.
When the HP finds a valid share, in addition to standard share data, the HP will generate a secret and send a blinded message (B_) to the pool. The inputs for this blinded message could be done at an individual ASIC level or as part of a farm proxy implementation, with the latter seemingly ideal for larger farms. This blinded message (eShare) would be included in Sv2 channel messaging as a protocol extension. This signals to the pool that there is a valid share and requests a signature using the appropriate key from the active block_keyset. The same blinded message could be reused multiple times as long as special consideration is given on the pool/mint side for tallying these submissions. Reuse of blinded messages may be necessary during implementation if computing these blinded messages is too costly for a given HP, otherwise a new blinded message should suffice and lower complexity.
When the pool receives an eShare, it first validates the share itself, as usual. Once validated, the pool signs the blinded message, completing the DHKE and providing the blinded signature (C_) back to the HP. This share + blinded signature are then added to the time ordered TIDES defined share_log. The HP retains the blinded message data inputs (x) and the unblinded signature (C) as defined in the Cashu protocol NUT00 1.
This share process continues until a new difficulty adjustment occurs, after which a new keyset is issued with appropriate difficulty targets, OR a block is found by the pool. A keyset rotation after a difficulty adjustment accounts for new share target difficulties. A keyset may be reusable across difficulty adjustments as a % delta from network difficulty.
When a block is found by the pool, a full list of shares and associated blinded signatures is published by the pool. This signals to the HP that the eHash shares are available for redemption. Now the pool references the share_log using the share_log_window (defined in TIDES) for what eHash is eligible for redemption. As HP’s redeem their eHash, the eHash is recorded alongside the public record of shares and blinded signatures as defined in the ecash Proof of Liabilities 5.
Redemption of eHash can be any of the available Cashu or ecash mechanisms appropriate for the HP.
Other thoughts:
Cashu supports spending conditions, such as P2PK (NUT10 1 and NUT11)
the blinded message secret uses hash_to_curve(x) computation which could be offloaded to an ASIC, maybe.
Since this is an ecash usage, Fedimint is also a viable option but has not been considered in depth.
P.S. I look forward to feedback and considerations I may have missed. This post was an effort to solidify my idea into something more concrete and shareable. A vocal (and probably less comprehensive/coherent) monologue of this idea can be found here. I hope to create a diagram to help illustrate this proposal.

2024-04-23 18:42:55 UTC

@npub1xts…kk5s
https://image.nostr.build/1e1cc22819189717ab4b59c28f18f534c14d51a3acc3a1fc4522ab84780ef746.jpg

2024-04-20 15:16:37 UTC

Anything cool happening in #ecash?

2024-03-20 13:56:12 UTC

- reply

🫂

2024-02-06 02:37:51 UTC

It's been a bit. What's happening in #ecash?

2024-02-06 02:37:02 UTC

- reply

based.

2023-12-15 17:39:40 UTC

test

2023-12-06 20:54:51 UTC

zaps on stream not working for CD. node didn't immediately show payments going through. generational wealth gone now. 😅

2023-11-17 16:29:21 UTC

- reply

sounds like a pitch deck waiting for Ten31.
Do you have payroll experience?

2023-11-13 02:20:35 UTC

https://github.com/fedimint/fedimint/pull/3583
Want to use FROST to do nostr things? Try it out with the nostrmint module. Technical skills needed to get up and running.

2023-11-01 13:13:36 UTC

https://image.nostr.build/973529a87f37ade065d0a05559bd63f7a3a3d97f814c54ff44142d9dd9122e97.jpg

2023-11-01 01:51:41 UTC

- reply

This is decentralization but rather redundancy. And yes, this is the fedimint model. There are multiple servers running fedimint and coordinating with each other to keep the mint "alive".

2023-10-28 02:17:11 UTC

- reply

https://void.cat/d/Jd164tbMJwrp9s1skpKsbS.webp

2023-10-25 17:47:35 UTC

@npub15hvkk66pfgffwklusrexwgwgq5c8prlwqputh9gwcsv27jfmdxzsa6gjgu
FEDIMINT'S CAN HELP WITH INITIAL MICROPAYMENTS BEFORE THE SATS AMOUNT REACHES ECONOMIC REASONABILITY FOR LN FEES.
https://github.com/MutinyWallet/mutiny-node/tree/fedimint
MUTINY EXPERIMENTED WITH THIS IDEA. TBD IF IT WORKS OUT THAT WAY.

2023-10-22 22:05:37 UTC

Any good diagram on how FROST would work? Like a flow chart one?

2023-10-20 22:40:16 UTC

https://gist.github.com/LaurentMT/e758767ca4038ac40aaf
anyone savvy on this stuff and have more resrouces?

2023-10-17 17:08:41 UTC

- reply

Fedimint is a federation ecash system (and can be much more since it's modular). Cashu is a non-federated ecash system. Both take in bitcoin and issue ecash notes. These ecash notes are 1:1 IOUs for bitcoin but use blinded signatures by the mint to preserve privacy. They also use LN for interoperability between other bitcoin projects/wallets/etc.
happy to go further if this wasn't detailed enough.
also check out https://fedimint.org

2023-10-17 12:19:41 UTC

- reply

It shoudl "just work". Fedimint uses LN nodes are liquidity between each federation and the general LN network. Or you could redeem for on-chain from Bob's mint. This is one part of the UX that is being explored and actively discussed/developed. There's really only one mature client app for fedimint and that's Fedi. I don't have insight into how they do things exactly.

2023-10-16 12:44:32 UTC

- reply

bank run. proof of liabilities is an unsolved problem. I do wonder about BitVM being applied to this problem in the future.
more to read here on Proof of Liabilities by @nprofile…4n7r
https://gist.github.com/callebtc/ed5228d1d8cbaade0104db5d1cf63939

2023-10-16 12:43:09 UTC

- reply

Fedimint uses something called a LN gateway. This is a LN node operator that runs a specific plugin/daemon alongside their node and can offer their liquidity to the fedimint. They're essentially a specialized client of the federation that deals in ecash<->LN contracts. If a LN invoice is given for internal to the mint, it just settles out ecash and the LN isn't touched.
I can get a bit more technical if you're LN tech savvy. or join the Discord and pop into #lightning to chat (chat.fedimint.org)

2023-10-16 12:40:09 UTC

- reply

Thanks! The speed at which you can bank run with an ecash mint is blindingly fast.

2023-10-16 02:03:36 UTC

- reply

No worries! imho, the naming was an interesting choice. But there's something to branding for easy mental mapping that can be respected.

2023-10-16 02:01:22 UTC

- reply

Yup! I've had the pleasure to meet Obi. Awesome dude. I've gave that one a listen.

2023-10-16 02:00:32 UTC

- reply

I messaged you... somewhere...

2023-10-16 01:55:54 UTC

- reply

Check out https://www.fedi.xyz/builders
They're a company running fedimint things and help on the protocol. Otherwise, it's really just technical people experimenting and iterating on this new and emerging protocol/tech.

2023-10-16 01:54:38 UTC

- reply

> My most pressing question is what is being done to help educate new users about what these technologies do and how to use them safely?
This note. 😅 But seriously, it's one of my longer term goals is educating people on the topic and generally being a "developer advocate" aka professional tech shill. There's not a lot of content out there focused on it... yet. There's https://fedimint.org and https://cashu.space/ available for consumption and several podcasts on the topic. But as with anything bitcoin, there should be more podcasts.
> That’s a lot!
Definitely, that's why both ecash implementations have opted to do invoicing like lightning for payments and such. You can still dump `cashu...` notes everywhere but otherwise it can be just lightning style payments/interactions. @nprofile…2edj is doing big things on this front and with nostr.

2023-10-16 01:49:36 UTC

- reply

2. I have no idea. For Fedimint, someone else can run the lightning node for you and the fee is configurable. For Cashu, I've never run a mint.

2023-10-16 01:48:52 UTC

- reply

1. because you want ecash? it's offline capabale. the data is the asset. You can receive it on a piece of paper. you don't want to manage liquidity. you don't want the latency of VPN/TOR. you have a service where you already custody users funds and want to provide a different privacy trade off.

2023-10-16 01:44:55 UTC

- reply

the mint is holding keys for the bitcoin backing everything. there can be no guarantee. But there can be trade offs. Only running "the right" code is helpful, but really it comes down to trust and risk appetite. I deposit very small amounts in some Cashu mints just to experiment, because I don't trust it enough with larger amounts.

2023-10-16 01:42:54 UTC

- reply

offline payments.

2023-10-16 01:42:39 UTC

- reply

no. some might disagree depending on your terminology. It's privacy preserving 1:1 bitcoin IOUs in a federation model. imho, that's not the coolest part though, it's the module system that enable you to have small consensus of servers on arbitrary data.

2023-10-16 01:41:26 UTC

- reply

Trust nothing. The trust is based on the relationship between users and the fedimint guardians aka node runners. See here for a more technical answer about proof of liabilities: https://gist.github.com/callebtc/ed5228d1d8cbaade0104db5d1cf63939

2023-10-16 01:38:23 UTC

- reply

Setup is a bit of work. Running is like any other server. Complexity to run is simple but early. Early stages for most users on the Fedimint side.

2023-10-16 00:25:05 UTC

- reply

#Cashu is one #ecash implementation. #Fedimint (what i work on part time), is a different implementation. Cashu is much more mature in its UI/UX so you're more likely to have encountered it. Especially here on nostr.

2023-10-16 00:21:56 UTC

- reply

I don't work at Fedi but that's probably the app. Fedimint the open source project just hit versioned release at v0.1.2. Very new but has been in development for a long time. Fedimint is modular as well so not just bitcoin ecash. Working on making the Fedimint have an npub myself (very slowly).

2023-10-16 00:05:54 UTC

hi nostr.
I'm working on fedimint (thnx @nprofile…shpv ) and have general interest in ecash.
if you don't know what that means, what's your most pressing question? if you do, when was the last time you've checked in on the space? It's quite interesting.

2023-10-16 00:04:25 UTC

https://github.com/fedimint/ui/issues/101
"Gateway admin UI packaged as an LnBits extension"
@nprofile…qadu since you probably have a lot more free time now that you've defended your thesis. Any time to ponder on who might be a good help for this?

2023-10-14 11:05:07 UTC

- reply

It was some svg with wavy thicc lines.

2023-10-14 02:49:48 UTC

- reply

Why not just further divide the existing coins? More numerically but you're not diluting the % of the whole that people own.

2023-10-12 13:11:50 UTC

- reply

only somewhat. I do think ecash should have a specific symbol/emoji.
@nprofile…c8fu suggested 🔩 because NUTS + BOLTS = ecash
Where did you derive you icon from?

2023-10-11 20:43:04 UTC

- reply

How’s my PR looking?

2023-10-10 16:11:26 UTC

@nprofile…7pym Is nostr a good place to reach out?

2023-10-10 15:36:01 UTC

- reply

let's make fetch happen.

2023-10-10 14:56:02 UTC

https://git.v0l.io/Kieran/snort/pulls/648#issuecomment-3620
🔩
@nprofile…2edj ?

2023-10-10 14:28:14 UTC

- reply

https://git.v0l.io/Kieran/snort/pulls/648#issuecomment-3620

2023-10-10 10:19:33 UTC

Ecash is just data. It can be shoved into almost application without major refactoring. I look forward to games build around ecash mints.

2023-10-10 10:18:26 UTC

- reply

Fedimint modules could enable swaps points. 🫣

2023-10-09 01:01:44 UTC

https://nostrnests.com/nyv3uf
Is this thing on?

2023-10-09 00:38:45 UTC

So fedimint nodes have a liveliness for connectivity. They connect over websocket to each other. This is how messages are passed and consensus communications happen. I wonder if there's a timeliness to consensus items, or if it could be done very slowly. If it could go slowly, then I ponder if you could just use nostr as a communicaiton layer. 🤔

2023-10-09 00:31:36 UTC

Is there a group chat for @npub1ndkltu98tr2eupgv5y367cck7kgj96d56vzmz40mxa25v68evv0qv6ffdn users?
I need to implement AsRef<[u8]> for Event and am curious if I should just Serialize it first or if there's a better way. fwiw, I'm doing nostr + fedimint things

2023-10-08 01:47:47 UTC

- reply

CC: @nprofile…j8hs

2023-10-08 01:46:41 UTC

https://github.com/EthnTuttle/awesome-ecash
@nprofile…p2kw @nprofile…2edj @nprofile…qadu
and @nprofile…70d7 since you like lists of things.
Ecash.Review
Do you have the domain yet?

2023-10-07 12:27:09 UTC

- reply

Nothing is secure from agencies. They own your device if they want. The telecoms own all mobile devices. Once you have the keys from the device, decrypting e2e comms is trivial.

2023-10-07 12:26:00 UTC

- reply

Fair point on the technically competent piece but I point back to wifi. That seemed unobtainable to many for a number of years and is now ubiquitous. You now longer have to get some external card to slide into a slot on your laptop to get wifi. It just works ™️
You point presupposes that humans won’t learn and adapt to using new technology over time. I disagree. The motivation to learn the tech or to abstract the tech to simpler UX exists and grows with time.
Look at bitcoin itself. You used to have to run CLI commands to interact with the network. Now…

2023-10-07 12:22:20 UTC

- reply

This is not a BTC specific issue. Using a 100 dollar bill for payments is the same thing.

2023-10-06 17:22:16 UTC

- reply

Why can't ecash be for payments? I personally wouldn't want large amounts of long-lived amounts stored in a fedimint. The former reducing overall rug risk and the latter reduces the chance of inflationary practices (aside from running a client that validates the version of fedimint run by guardians).
Fedimint doesn't explicitly have to be a "bank", although, admittedly, that's been a advertised use case from louder voices than mine own.
Laying out an example:
I'm visiting LA. I somewhat know people in the area, maybe I'm visiting them. There's a smaller network of merchants that participate in a fedimint. Similar to handling cash, they don't keep large amounts in the drawer (in the fedimint). Just enough to do business of the day. When i arrive, I can peg-in (on-chain or with LN) to the fedimint and now have ecash to spend. Each merchant and myself don't have to mange LN nodes and the complexity inherent to it.
Another:
Remove the ecash/BTC/LN modules and insert a password manger or any other arbitrary data. Since the data is validated via consensus among fedimint nodes, the risk and access is distributed. It enables the syncing and validity across disaggregate nodes.
I personally would love to auto-sync my bitwarden instance between home and office servers. I understand there are solutions to that with some automation, but fedimint could offer this out of the box for the less technically inclined.
Myriad of solutions and fedimint could be one. Definitely not the end all be all, but i have to pick something to focus on with my limited time. 🫠

2023-10-06 11:40:56 UTC

- reply

Are you aware of the Hawala network?

2023-10-06 02:13:43 UTC

@nprofile…vjma
Used my NIP05 for diffussion.to
Very sad there was no way to verify [email protected] for the site.

2023-10-04 14:20:15 UTC

https://bolt.fun/story/nutstash-newsletter-6-deterministic-secrets-and-recovery-from-seed--1080

2023-10-04 13:30:57 UTC

- reply

1. And now most of the world trusts banks with their "money" (currency really). I don't think this paradigm will go away and making people comfortable with the personal responsibility of holding all of your wealth yourself will take a long time. In the meantime, custodians are going to exist. Giving people a privacy preserving trade off for a custodian seems a good way to move toward a better future, while we educate the masses on self-custody and personal responsibility.
2. Agree with all of this. Trade offs always. There is going to be complexity with any technology until there's not. It used to be super complex and require lots of people to run mainframes, and now we have super computer in our pockets. The more time passed, the more abstracted away from electrons on a motherboard we get. Even 10 years ago, managing a single bitcoin wallet was a super technical task, but today I can download an app to my phone and hold the keys to some coin.
3. I get your point here and don't disagree. This is why I dedicate my free time to working on a solution that I think will help adoption of bitcoin. The "coin" with the best tools will capture more economic share. I hope you're building your ideal future as well. (Personally, I think ETH will be what they build the CBDCs on. All the code and infrastructure is there for the State to scoop up.)
likewise, thanks to you for the reply.

2023-10-04 01:12:32 UTC

- reply

I have no writing on drivechains, but I won't be considering them until mining is more decentralized. Hopefully Stratum v2 will help this along, then I can consider putting more economic weight onto mining. The mining ecosystem seems ripe for State capture with the trend toward centralization (look at the three biggest mining pools). Adding drivechains now, (which enable "crypto" tokens, to my understanding) seems like it would draw more attention from the State, given all the recent crack down on crypto more broadly. Landing Sv2 can help disperse the mining risk before we add some other reason for the State to crack down. Maybe in a decade, I would consider drivechains seriously and do more research. For now, I am crunched for time and bandwidth so plan to focus on things I can build now that are helpful.

2023-10-04 01:05:25 UTC

- reply

> A fedimint of a group of 5 is also liable to the risks of 5 peoples lives.
There is a threshold quorum to move funds? so the majority of these 5 would have to collude to aid the one child.
> The whole basis for fedimint is based on an anthropological error made by wealthy westerners AND wealthy disconnected Africans about the people they are trying to help.
I don't claim to understand any culture other than my own (western), and even saying that would be a stretch, so your assertions of other cultures outside of western culture may or may not be accurate. However, it does seem that you're only considering one use case of fedimint and not other cases. It's a modular system that can be extended to custody and reach a threshold consensus on arbitrary data. Taking custody of bitcoin is only the default use case. I anticipate many more to be developed.
Multi-national corporations can custody their money and data across jurisdictions in a secure way. Market providers can build an entire ecosystem around their market with modules to customize how the marketplace works. Offline payments with ecash open up a whole heap of other use cases, for example, I only accept communications with valid ecash attached to them.
-----
we already covered the writing critique in another thread. 😅

2023-10-04 00:51:47 UTC

- reply

When you say "most people feel this way", what part of the world are you referring to?
What downsides are you referring to? please elaborate. There are plenty of trade offs in all things, but if you're more specific, I can better address the concern.
In your last paragraph, are you referring to another "coin" aside from bitcoin? It reads like you are but you're unspecific. Also, the ad hominem attack doesn't help convince anyone. Give me real arguments. What coin are we waiting for network effect to increase? The market has been pretty clear on what it values the most at the moment.

2023-10-03 20:28:59 UTC

- reply

Not my site. 🤷‍♂️ sorry. @npub1p4k…cxf8

2023-10-03 20:05:45 UTC

- reply

Don’t have any hard estimates but I would think end of 2024 might be a good timeframe. Just hit 0.1 so very very early.

2023-10-02 20:21:45 UTC

- reply

bank run not because there are no funds, explicity to audit the fedimint. Since this can easily be coordinated and executed, there is risk to fractionally reserving. See here for more on the Proof of Liabilities thoughts (not mine)
https://gist.github.com/callebtc/ed5228d1d8cbaade0104db5d1cf63939
I have no idea how XMR works, but it could probably be integrated using the fedimint module system.

2023-10-02 15:56:31 UTC

- reply

You chain that bike up?

2023-10-02 15:50:28 UTC

- reply

Taxis?