shocknet_justin
Justin (shocknet) ⚡

Ran the numbers and it's possible to get $1500 or so worth of API tokens out of a $20 GPT Plus subscription with codex auth
Makes no sense
Composer-maxxing for $60 with included credit to other models still the best deal though

2026-06-18 18:20:25 UTC

- reply

CLINK author here, I like keysend, its actually been one of my arguments against Bolt12... Bolt12 should have never happened, add that to the diagram and CLINK is dead simple by comparison.
Couple limitations though with keysend that CLINK addresses though:
1) Web friendliness, if Lightning is to be the money on the web it needs to work in websites, which nostr does
2) CLINK keys are de-coupled from the node itself, so are available per-user rather than per-node in shared node contexts
3) Arbitrary payer_dater for commerce, product sku's etc in the payload (also receipt payloads which also enable interactivity on webapps)

2026-06-18 01:18:54 UTC

- reply

Connect to and manage your node over nostr to avoid network setup
Manage clink offers for products services
Accept and manage debit requests
Sync across devices
Invite guests to your node
Automate payments
Uses nostr for identity/device sync
Multi connection multi identity
Static payment pages (payges) over nostr
Reference client and management dashboard for Lightning.Pub
Probably more I'm forgetting

2026-06-17 20:15:24 UTC

ShockWallet is now published in the @npub10r8…t2p8
https://cdn.nostrcheck.me/1ef5788b8c08e276fab7c0737c2227aa2074e324a41b9499d8ad39d8fba8d245.png

2026-06-17 02:16:56 UTC

- reply

Yea IP traffic is at a much lower level than is in scope, even the underlying lightning node still has to squawk over its native port. Need some kind of tunnel to obfuscate a residential IP
I usually suggest a cheap VPS and just use its IP through SSH -R
Much better reliability

2026-06-16 23:44:25 UTC

- reply

Since the CLINK keys are decoupled from the Lightning node you can roll them without losing channels, you could have multiple for different apps/users/use-cases to break correlation, or use blinded paths to obfuscate the destination node
Relay observers can see DM metadata of course, but since they're scoped only to these ephemeral kinds there's little to glean particularly where the payer is typically using an ephemeral key.

2026-06-16 23:29:05 UTC

- reply

Bolt12 does nothing for privacy, blinded paths maybe do (debatable) but exist outside of Bolt12 (LND has had them for a long time already)
CLINK is better for static addresses, and more private since it's decoupled from the node, allows for HA, and is out of band on a web port.
(static addresses are a misnomer because Lighting is inherently synchronous, they're just pointers to a live endpoint)
Bolt12 is literally just invoice passing over Tor-like onion messages, fortunately LND has an option to disable them. Since you can't inspect them you can't block non-invoice data, Bolt12 is a vulnerability pushed by the minor implementations who went all in on phones-are-servers. Dumbest thing ever.

2026-06-16 23:17:03 UTC

- reply

I know, they're adding Bolt12, they capitulated to retards that cried for it despite knowing better.
Completely moronic to use Lightning nodes for arbitrary data onion messages.

2026-06-13 21:25:07 UTC

- reply

I'm the anti-Bolt12 guy
It's retarded for many reasons

2026-06-13 21:22:16 UTC

- reply

There's Nostr CLI tools written in go or rust if that's your thing... or even websocat if you're elite
But if channels are so hard that you're shitcoining with a low-anonset clown chain then there's nothing more that can be done to help you, you've got privacy larper syndrome

2026-06-13 18:48:29 UTC

- reply

Wtf you talking about Willis?
Since CLINK is Nostr, it works literally everywhere.
bxrd.app and shockwallet are both PWA's
The reference server is a nodejs app that sets up in a minute and can run on any VPS or whatever box you have at home... but because it uses nostr it obviates the network setup.
You can even use a noffer as a url param to a web site:
https://pay.shockwallet.app/?noffer=noffer1qszqqqqqzspszqqzg3jxzv3evccngdryx33kyct9v5ukyenrv4jk2vesv3jnscfcv5mnzerrxpjkxce3xajnzef3xvenqvn98qcxxvfkxucnzerzxyervvnrvvekyvsprfmhxue69uhhxarjvee8jtnndphkx6ewdejhgam0wf4sqgrka4zlqr820wk9nkxsklfqfpy02vva0wtvzs8lkm7t424s5y75fcqxs9tw

2026-06-12 15:56:25 UTC

- reply

💯, LNURL can do this as well just to a lesser degree
Next steps for us are to add products in bxrd, so in addition to your shitpost feed, you'll be able to create products for sale and your profile becomes a storefront
It'll also be going into Lightning.Video so that it becomes fully self-custodial, a noffer on each video will let your Pub trigger paywall unlocks
CLINK manage `nmanage` is a 3rd spec in the suite that will allow bxrd/lightning.video/whatever marketplace apps that use it to create offers from their own UI so you don't have to do that manually in shockwallet... you'll just create a product in the marketplace app, that app will reach into your Pub over Nostr to set up the appropriate offer and use it in the product listing
This is a POC of a static website that parses noffers to pull invoices that demonstrates how product links will work... the beauty of nostr is it works on the web and can just show bolt11... wallets don't need CLINK to work with those, bolt11 is the lingua franca
https://pay.shockwallet.app/?noffer=noffer1qszqqqqqzspszqqzg3jxzv3evccngdryx33kyct9v5ukyenrv4jk2vesv3jnscfcv5mnzerrxpjkxce3xajnzef3xvenqvn98qcxxvfkxucnzerzxyervvnrvvekyvsprfmhxue69uhhxarjvee8jtnndphkx6ewdejhgam0wf4sqgrka4zlqr820wk9nkxsklfqfpy02vva0wtvzs8lkm7t424s5y75fcqxs9tw
@nprofile…gcsu @nprofile…r72v also have a kiosk powered by an offer to let people pay for snacks https://shocknet.github.io/PlebCafe/

2026-06-12 15:31:33 UTC

- reply

Ah, that explains it
Payer_data tells the handler what payload should be expected along with the invoice request and if the shape doesn't match it's rejected
payer_data is arbitrary json that can be used for product info, sku's, an email address, anything you want to pipe back out to another system upon payment (works with the webhook callback)

2026-06-12 15:17:48 UTC

- reply

Server can respond that they expired (as a reason the pointer is no longer valid, code 3)
But I see this is from our Pub, it's logging invalid expected data and responding with a 1 (generally invalid, not expired)
It doesn't recognize the pointer... there was an IPC crash so it might not have stored... investigating that on our end

2026-06-11 23:49:26 UTC

- reply

My client isn't treating ones in a note as a zap, it's just fetching the invoice and paying it
But, I also just zapped you from the zap icon which does send the zap payload (prioritizing a published noffer over lud16)
Could treat the post noffers as zappable... just a matter of clients sending the payload they would regularly
https://cdn.nostrcheck.me/b81d9e014625f0652d42ccd3df7e46127110356644eff5249d4b981bdef84763.png

2026-06-11 23:29:05 UTC

- reply

https://cdn.nostrcheck.me/b3f72d3d17184c3e7e9195db5b1bc595f09b8872a6f5e5c2e8feb0961a084192.png

2026-06-11 15:14:34 UTC

- reply

I had opposing feedback that people wanted to see what they zapped (ex if you send 21, sats show 21 sats, fees in the modal) but that's a good preference toggle we could add to show the total now that you mention it
Bootstrap is for convenience and stacking LSP credit, it's really meant to connect to a self-hosted Pub. Floor 10 is just a safe default for an operation... still much lower than Spark/Ark/Liquid swap services

2026-06-11 15:02:40 UTC

- reply

Paid 12, the floor is 10 or 60bps
Percentage is high because it's small, 1000 sats would have cost 60 sat

2026-06-11 14:51:28 UTC

- reply

Reserve is held for routing fees on LN, amount held must exceed sending since the sender pays
Total fees are shown on the item including service, click one of the outbound payments and you'll see those in the modal there

2026-06-11 14:10:53 UTC

- reply

Should be the fee reserve, it's shown in the send screen

2026-06-11 04:12:12 UTC

CLINK is an onomatopoeia for the sound of coins changing hands

2026-06-10 20:49:37 UTC

- reply

Rarely, exit nodes typically trigger fail2ban because they DoS constantly

2026-06-10 20:40:36 UTC

- reply

Looks ok with nos2x, we'll set up an alby to try and repro, thanks for the report
There's no social features hooked up yet so you can just generate a throwaway key in local storage for testing

2026-06-10 20:32:45 UTC

- reply

Bizarre... whats the offer? I'll try to repro
Fixed something potentially related the other day, what's the version code in the bottom of the nav bar?

2026-06-10 20:19:27 UTC

- reply

ShockWallet or Zeus
ShockWallet has as PWA if you want to test on the fly and not install an app: https://my.shockwallet.app
If you already have a wallet connected via NWC it shouldn't matter though, just use the noffer in-app to get the invoice and pass the invoice along.

2026-06-10 20:16:12 UTC

- reply

Bingo, unfortunately for Lightning disrespectors its the only model that fits this, with an asterisk on the everyone part since Bitcoin itself does not accommodate everyone.
An exit of any construct has to work withe same properties Lightning does, the user needs a non-dusty amount just to get into the court room, nevermind making such a case worthwhile.
The fake L2's accordingly have to use Lightning as the lingua franca between one another, because they are closed networks / applications that fall short of this model.

2026-06-10 19:59:48 UTC

- reply

Indeed, the problem with L2 security is that it is inherently dependent on liveness, since they are multi-party and the chain is the adjudicator that needs to be reached.
If you fight liveness, you sacrifice security, and such a solution is back to being just re-branded trust.
This is why I laugh at these fake L2s, it's not about the L2, the L1 is all that matters, and people beefing on Lightning just don't like Bitcoin.

2026-06-10 18:50:53 UTC

- reply

Yea my framing is in a hypothetical scaling scenario to entertain the "we must scale to 8BN people that don't have any money" virtue signals people use to justify shitcoining.
I personally think that's retarded, but it undercuts these fake L2s re-branding trust and centralization.

2026-06-10 18:04:45 UTC

- reply

Unilateral chain exit is subject to the constraints of the chain itself, not the L2. The gripes about Lightning are because of this, not Lightning itself, beefing with Lightning is beefing with how the chain works underneath it.
Since supply being the only real scaling limitation if we're talking about billions of users, L2's cannot scale sovereignty until the chain does.
You can't unilateral exit millisats if the chain does not recognize millisats for example. No L2 can solve this.

2026-06-10 17:55:39 UTC

- reply

> We can arbitrarily divide on any L2
But you can't offer the chain's security with those, so all roads lead back back to trust and centralization.

2026-06-10 17:49:23 UTC

- reply

Now I feel dumb at math. Great post.

2026-06-10 17:07:25 UTC

- reply

It 10x's the base unit because Bitcoin doesn't have floating point

2026-06-10 17:06:37 UTC

- reply

Have fun with that.

2026-06-10 17:05:08 UTC

- reply

Yes it does. Bitcoin is the sum of its base units.

2026-06-10 17:04:50 UTC

- reply

Again, Bitcoin doesn't have decimal places or floating point precision.
It's not a math question. It's the reality of how the protocol works.

2026-06-10 17:02:57 UTC

- reply

It is an increase in supply, because Bitcoin is 2.1q.
An increase in base units is not necessarily dilutive.
These are not incongruent.

2026-06-10 17:00:04 UTC

- reply

Those were soft forks, a base unit change i'm fairly certain would need to be a hard one. I could be wrong on that, popcorn ready either way.

2026-06-10 16:52:14 UTC

- reply

I literally just said I'm not talking about dilution.
Dilution was projected by you and low-attention-span guy.
How is this for clarification, "scaling requires a supply increase, but that supply increase doesn't have to be dilutive."
Point remains, it's not going to happen but I got popcorn ready if you want to try.

2026-06-10 16:45:39 UTC

- reply

> could be changed
via a *supply increase* of the base unit
You're talking about *dilution*, like the other guy, which I never said. I'm being literal, factual.

2026-06-10 16:36:16 UTC

- reply

Chain transactions are done in sats. There are no decimals in Bitcoin, it does not have floating point precision. The base unit is sats, there are 2.1q of them.
A UI rendering 100 sats as .00000100 Bitcoin does not change the fact Bitcoin is using sats, not decimals.

2026-06-10 16:27:50 UTC

- reply

Bitcoin doesn't have decimals, it has sats. "Whole coins" are an abstraction, a Bitcoin is 100M base units, sats.
You can't add abstracted decimal places without a supply increase of the base unit, which would break every piece of Bitcoin software ever created... it's not going to happen.
2.1q sats -> 21q usats or whatever is a 10x supply increase. The hardest fork imaginable.

2026-06-10 16:23:25 UTC

- reply

Not on-chain they don't, you don't seem to understand the difference between internal accounting and actual Bitcoin, maybe why you think a shitcoin like Liquid is Bitcoin...

2026-06-10 16:21:17 UTC

- reply

No you can't. Adding decimals in Bitcoin is a supply increase, a change in the base unit, not going to happen.
msats in Lightning aren't resolvable on chain, they're shitcoins used for internal accounting/rounding... they aren't units of actual Bitcoin.
You really don't know what you don't know...

2026-06-10 16:13:38 UTC

- reply

This is Bitcoin 101 fella, it's not divisible at all.
2.1quadrillion sats.

2026-06-10 16:07:54 UTC

- reply

It's a mathematical fact 8BN cannot use Bitcoin, they have to trust someone to use it for them, because it's not divisible and chain representation has a minimum.
Ark is a scam from the bottom up.
What you believe and what are true can be separate things. I acknowledge reality and focus my energy on what is possible, not cope and virtue signals.

2026-06-10 15:59:08 UTC

- reply

Actually if you dont have a CLINK Debit string it should just show the invoice for scanning... just confirm you're auth'd...

2026-06-10 15:58:14 UTC

- reply

In settings add a CLINK Debit string to connect to a spending wallet. It will take the invoice from the noffer and pipe it over to the debit connection.
If you already did that, are you signed in with an extension? there was a bug with those but was fixed...

2026-06-10 15:55:38 UTC

- reply

> There are no solutions. Only tradeoffs
Exactly. Those trade-offs are trust and centralization, which are all fake L2's can offer.
You cannot handle 8 billion people without trust and centralization, that's a function of the supply cap / dust + non-zero fee required for chain security. Bitcoin scales to 100-200M at most, less as large accumulators remove float, that's purely on lack of divisibility alone and has nothing to do with tx density.
8BN is also not the goal, that's retarded. Not even 8BN have internet or phones. There are only 300MN businesses and maybe 1BN households.
The only tradeoff lightning makes is liveness, which is how the internet works. That's a hard requirement for anything but the base chain.
It's a fact that trust and centralization are the only levers, but if you want to beat your head against the wall denying reality like shitcoiners do have fun I guess.

2026-06-10 15:40:26 UTC

- reply

Based, let me know when I should add it to the apps lists.

2026-06-10 15:31:49 UTC

- reply

> You can't solve the core issue.
That's what I've been saying, the only levers to pull are trust and centralization.
> there can be no other emergent L2
That's a fact created by those unsolvable core issues, another "L2" that attempts to solve perceived issues in Lightning can only do so by adding trust and/or centralization, which make it NOT an L2.
Ark is a scam. VTXO's are not real. Liquid might have acceptable trade-offs for many, if it were honest, it's falling into the scam marketing trap by pretending to be an L2 and self-custody.
Nothing can be made better than Lightning, because Lightning faces unsolveable issues. Trust and centralization are not solutions.
Decentralizing trust is the only realistic mitigation, and that's why Pub focuses on that.

2026-06-10 15:21:18 UTC

- reply

🤝
https://cdn.nostrcheck.me/4705250d166d6e833d62c029fc10340409994ebd2de0f66e3e74fe53774902a8.png

2026-06-10 14:52:47 UTC

- reply

Nothing does, as I started off with, the only lever to pull is trust. I just localize the trust.

2026-06-10 14:51:05 UTC

- reply

People are going to use custodians, that's a fact.
I'm decentralizing the custodians. Shared lightning nodes locally.
Pretending liquid and other fake L2 dog shit aren't custodians doesn't change that, it's cope. Centralizing cope.

2026-06-10 14:48:21 UTC

- reply

It's the exact same, custod6is custodial. At least uncle Jim nodes localize trust to where it exists already, the house/business/community.
Liquid is centralized custodial. Peg, lol.... What they user holds is ious.

2026-06-10 03:22:17 UTC

- reply

Can also set it in your nostr profile with bxrd
https://cdn.nostrcheck.me/27862d68ebb9b3b44a6cf8efecca468e83c33d9fb8b01bd3201915980ab3d4f4.png

2026-06-10 03:18:28 UTC

- reply

Tag me on the update PR for NIP-57 that removes lud16 and I'll be happy to ack if the replacement signal is even marginally sane.

2026-06-10 03:09:29 UTC

- reply

> This is just another NWC
> You are not a NWC competitor
> why the need to reduce what NWC is?
> you are abstracting Lightning addresses
I'll look at the payto: thing, but until nip57 removes lud16 then kind-0 is the upgrade path. Until you can point to an inaccuracy or
CLINK Debits are already replacing NWC in several places, and that's only a fraction of what CLINK can do.

2026-06-10 02:48:09 UTC

- reply

Sure it is. No one seriously debates this, calling it a federation (lol) doesn't change this fact.

2026-06-10 02:35:22 UTC

- reply

Different properties, far more functionality, but same? Sounds like cope.
NWC couldn't replace lightning addresses because it's backasswards.
NWC is another way of coding of kind 21000, but without taste or vision.

2026-06-10 02:22:04 UTC

- reply

Didn't need to, everyone already knows its custodial.

2026-06-10 02:20:37 UTC

- reply

Lightning Addresses are only for spontaneous payments, CLINK does far more than that.

2026-06-10 02:04:38 UTC

- reply

What point is that?

2026-06-10 02:02:25 UTC

- reply

Ok so it's not inaccurate, I'm open to hearing stylistic preferences. I'm for improvement.

2026-06-10 01:51:27 UTC

- reply

Until NWC gets a total rewrite to handle interactions, it's accurate.
Or would you like the receipts on Pub (kind 21000) predating NWC?

2026-06-10 01:39:38 UTC

- reply

Let me check my receipts drawer again
#nevent1q…g4ss
https://cdn.nostrcheck.me/c8116489b2580b0fabef4d3a9485cb5ed021259809052067a5bda3d14bba0259.png

2026-06-10 01:20:51 UTC

- reply

You might not like it, but it's reality. Got the receipts. And if it doesn't help transact value it has no value. Nostr users are overwhelmingly lightning users. You can't have decentralized wechat without payments. Nostr is a 1 legged stool without it.
I'm not the one that merged nip57 that introduced lud16, clink succeeds lud16.
If you'd like to propose a better signal, I'm open, but noteable that you didn't object to my prNIP-69 also using kind 0

2026-06-10 01:05:32 UTC

- reply

Reality is nostr is nothing without lightning, and would not exist without it.
But I agree about silent payments, chain addresses, bolt12 etc... all garbage that belongs nowhere near kind 0

2026-06-10 00:49:38 UTC

- reply

No you weren't, it was a 1:1 DM about GUN... ShockWallet predates nostr by 2 years.
https://x.com/i/status/1329817308378882048
https://cdn.nostrcheck.me/514d1d5e4b7cd62038ba01e778715a294bc9aec2108e31e758a5c2b8e7d8ff81.png

2026-06-10 00:45:28 UTC

- reply

Yes sidechains are fake, scams.
If it's not lightning abd calling itself an L2 it's a fake L2
Bitcoin scaling is not solvable, the supply is fixed and supply is sacred, nor divisible.
https://stacker.news/items/1275977/r/justin_shocknet

2026-06-10 00:38:30 UTC

- reply

Those clients then serve no purpose, unanimity is the lowest common denominator.
Nostr's genesis was literally to transport invoices and add context to lightning payments, everything is downstream of that

2026-06-10 00:33:04 UTC

- reply

I agree not everything belongs there, but lud16 and offers are critical profile information, nostr wouldn't exist if not for lightning

2026-06-10 00:31:16 UTC

- reply

Nope, lightning is emergent of hard constraints... No crypto theater can solve anything, fake L2's just smuggle trust and centralization. Shitcoins 2.0
If it's not lightning it's a shitcoin

2026-06-10 00:28:37 UTC

- reply

That's where lud16 lived so the most compatible option flow-wise

2026-06-10 00:14:23 UTC

- reply

There is no scaling solution to be had, Bitcoin is what it is.
The only lever to pull is trust.
Lightning.Pub localizes trust.

2026-06-09 23:59:46 UTC

- reply

tag me when it's live and i'll add amtheyst to clinkme.dev and repo readme

2026-06-09 23:58:41 UTC

- reply

Offers go in kind-0 metadata as clink_offer, or in NIP-05 payloads
Bxrd will prioritize kind-0 for zaps if present, then NIP-05, then lud16 if neither are present

2026-06-09 22:23:02 UTC

- reply

Done, but other clients really shouldn't be stripping line breaks

2026-06-09 21:34:45 UTC

- reply

What error?
The zap may have been using regular LNURL, will check that

2026-06-09 21:29:03 UTC

- reply

Added 🤝
https://cdn.nostrcheck.me/01284bca9629bd6f1fedab4dba03b6b89ab410ea30b78e69ac8c73804f9d8710.png

2026-06-09 20:43:43 UTC

- reply

What error did you get in bxrd?
Android string fix still stuck on google play review... checking on it
https://cdn.nostrcheck.me/0702e47dc0c979e44910456890d7eaf2c9fad466f2ed535299e61daea9ef9326.png

2026-06-09 20:08:34 UTC

- reply

Not seeing labels?
They should show in history but if you're not seeing them i'll try to repro
https://cdn.nostrcheck.me/0e4c84b53b5dbec1afeeb58457c4c8b33b764507895652295a580f932e65cf84.png

2026-06-09 16:20:20 UTC

- reply

Shot you a DM yesterday actually, what should I add to clinkme.dev for your stuff?

2026-06-09 15:52:33 UTC

- reply

Bxrd now renders noffers as a pay button
https://cdn.nostrcheck.me/2b9fd47875e0c8f7483dce2648ba993a8c10ab4b76d25e0962215f2216dc5bd3.png

2026-06-09 03:15:54 UTC

- reply

None I'm familiar with, but it should be trivial for someone familiar with their extension system to whip up

2026-06-06 14:13:36 UTC

CLINK ⚡

2026-05-31 18:56:41 UTC

- reply

On the first, you mean like personalized graphs? Graphs need to be hosted, could be a compelling premium option.
On the second, Sanctum policy engine integration in the works, with self hosted signer.

2026-05-31 01:16:45 UTC

- reply

A system that allows bots to DoS or drown out users with noise is censorship by other means
Transparent WoT removes the developer skew, gives users the upper hand over bots
Bxrd flock is ascendant

2026-05-31 01:04:06 UTC

- reply

You're being censored because *they* censor, not because of WoT
WoT is decentralized
You're surfacing just fine on Bxrd

2026-05-31 00:57:47 UTC

- reply

bot floods necessitate some kind of filter
Graph based WoT is the workable filter, auditable, reproducible, and without censorship
https://bxrd.app

2026-05-31 00:22:52 UTC

- reply

bxrd.app

2026-05-27 22:28:21 UTC

- reply

nostr is just websockets and json, those aren't going anywhere

2026-05-27 22:27:13 UTC

- reply

Yea a `clink_offer` instead of `lud16` would work just as well in kind-0, discussed this with someone today actually

2026-05-27 16:48:56 UTC

- reply

I think this is directionally correct, just the other day I ported nymrank from NIP-85 to a regular API because NIP-85 and relays generally are bad at delivering the ranks and other metadata of 200k+ keys... bulk is needed for a lot of things
Bulk reconciliation still needed a gzipped file endpoint to avoid pagination hell, but this may be a good start for the intraday deltas
Will have a closer look at some point and compare our shapes, would be good to have this standardized

2026-05-26 18:02:47 UTC

- reply

Tangent welcome. Personal server master race.

2026-05-26 17:53:04 UTC

- reply

Correct, the internet is inherently interactive.
Appeals to non-interactivity are silly, but not as silly as the privacy larp being used by people deluding themselves into thinking silent payments actually solve something.

2026-05-26 17:34:11 UTC

- reply

Lightning is the largest coinjoin.

2026-05-26 17:33:56 UTC

- reply

Bolt12 is literally retarded NGO Tor (unreliable) slop that doesn't work on the web, not a serious solution to anything.
That overly broad use of social isn't helpful, all payments are social by that standard. A silent payment only achieves removing the utility of labeled one-time addresses.
If your saying the real use-case is non-interactivity (also an anti-pattern imo), then we can quit privacy larping and call it that.

2026-05-26 17:20:04 UTC

- reply

> "privacy" apps spread through virtue signaling, not substance
Anything explicitly geared towards privacy is guaranteed to have the opposite effect. Honeypot dynamics and it leads people to be lazy or naive in their practices.