Layerz Wallet

Bitcoin-first self-custodial wallet focused on Layer 2 interoperability

[Layerz Wallet @LayerZWallet]

How fast can you receive a lightning payment without having installed a wallet or signed up anywhere?

This is how @Layerzwallet does it!

[Layerz Wallet @LayerZWallet]

@marvelboyHaRSH Still busy with testing, will be ready for next production release!

[Layerz Wallet @LayerZWallet]

Restore is the test, not a secure copy of a seed.

Wipe the phone. Type the words. Pay a BOLT11 from the pocket that came back.

https://t.co/5qXKd50IzF

[Layerz Wallet @LayerZWallet]

@virtuals_io Owner-set limits are the right instinct.

The failure mode is the agent holding the key.

Keep the pocket small.

Pause should kill the tools, not just the cap.

[Layerz Wallet @LayerZWallet]

@PayAINetwork Volume leaving test-mode is real.

Most of that spend still sits in a hosted account though...

Ideal flow ->

* An agent can pay a BOLT11 from a pocket you funded.
* Quote the swap.
* Execute in a controlled environment
* Cap what it can see.

[Layerz Wallet @LayerZWallet]

@callebtc A dozen agents on the code is fine. A dozen agents on a funded wallet is not.

If it can pay a BOLT11, fund a small pocket.

Pause when you sleep.

[Layerz Wallet @LayerZWallet]

@River The minimum understanding of SC is to restore the backup once. And do a real send.

If both work, we already agree on the part that matters in terms of self custody. The rest is a spectrum and is definitely not suitable in every scenario but those are outliers for most people

[Layerz Wallet @LayerZWallet]

@cakewallet @girlgone_crypto Great panel. Key test of Self-custody is an actual restore.

Backing up keys, screenshots (worst plan in history). Seed cards etc etc is an illusion if you have not wiped a device and brought the wallet back. Until then you only have a promise, you have not tested it yet.

[Layerz Wallet @LayerZWallet]

@ElectrumWallet BIP39 is a format. Restore is the test.

Wipe the phone. Type the words. Pay a BOLT11 from the pocket that came back. If that fails, the backup was a screenshot...

[@overtorment @overtorment]

Next wave of bitcoin hacks is gonna be AI-coded wallets that look legit, but actually rug-pull people.

With AI its trivial to make a fully-functioning bitcoin wallet.

Then its a matter of purchasing appstore accounts & fake reviews. Something that scammers are really good at (its all PNL to them)

Some gullible people will install it and load with funds.

Rinse and repeat.

That's why its important to stick to reputable ones, like @bluewalletio

[Layerz Wallet @LayerZWallet]

@lopp Always-online is the job of a spend wallet.

Keep it small on purpose!

[Layerz Wallet @LayerZWallet]

Nice work!

No channels is why a shop will actually turn this on.

The trade is the way out. If operators go quiet, you want a unilateral path you have already tested with a small sweep, not a sentence in a "readme"

POS can be easy.

The weeks takings should not sit on the L2 because the invoice was easy though...

[Layerz Wallet @LayerZWallet]

@Must_be_Ash @coinbase @PhotonHQ A brokerage API is one kind of risk. Sats are meaner. If an agent can pay a BOLT11, spend coin or Auth swaps...give it a tiny pocket you funded on purpose.

However treat it like you are the bank giving client access to tx functionality that you can pause at anytime...

[Layerz Wallet @LayerZWallet]

7/ Download, activate the agent, paste the MCP URL into Hermes or Claude.

https://t.co/5qXKd50IzF

[Layerz Wallet @LayerZWallet]

🧵1/ Hermes just added a pile of MCP connectors. Datadog, GitLab, Railway.

Your agent can read production now. It still cannot pay a BOLT11.

[Layerz Wallet @LayerZWallet]

6/ Desktop can run local-only, no public tunnel.

Open source: https://t.co/y7tKfEkwQx under shared/features/mcp/

[Layerz Wallet @LayerZWallet]

@CasaHODL @lopp The descriptor is the wallet. Lose it and the keys are an expensive paperweight.

Vault for savings. Separate small hot wallet for BOLT11 and Spark or other l2. Different jobs. Do not mix them.