What is Nostr?
s7r [ARCHIVE] /
npub1j3uā€¦wg9h
2023-06-07 17:43:26
in reply to nevent1qā€¦07vc

s7r [ARCHIVE] on Nostr: šŸ“… Original date posted:2015-10-14 šŸ“ Original message:-----BEGIN PGP SIGNED ...

šŸ“… Original date posted:2015-10-14
šŸ“ Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 10/14/2015 6:19 PM, Paul Sztorc wrote:
> LN transactions are a substitute good for on-chain transactions.
>
> Therefore, demand for on-chain transactions will decrease as a
> result of LN, meaning that fees will be lower than they would
> otherwise be.
>
> However, the two are also perfect compliments, as LN transactions
> cannot take place at all without periodic on-chain transactions.
>
> The demand for *all* Bitcoin transactions (LN and otherwise) is
> itself a function of innumerable factors, one of which is the
> question "Which form of money [Bitcoin or not-Bitcoin] do I think
> my trading partners will be using?". By supporting a higher rate of
> (higher-quality) Bitcoin transactions, the net result is highly
> uncertain, but will probably be that LN actually increases trading
> fees.

Probably yes. But probably no. Having less hashing power is not good,
and it's unrelated to scalability and decentralization, it's related
to security. Of course we could argue that the hashing power is not
super decentralized at this moment but it's unrelated to the topic.

I'd rather have less decentralized big amount of hashing power as
opposite to less hashing power.

One theory, very close to yours, is that if Bitcoin transactions
demand grows so high that we need the lightning network, there should
be plenty of on chain transactions for miners to collect fees from.

I haven't yet seen the incentives of everyone involved in lightning
network (payment channel end points, hub operators, miners, etc.) but
would it make sense to enforce a % of the fees collected by on payment
hubs to be spent as miner fees, regardless if the transactions from
that hub go on the main chain or not?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBCAAGBQJWHtksAAoJEIN/pSyBJlsR9Y0H+QE/XdW7yauhrNJtp2eIBPg9
zVUanzR2LT0zAkeF5/Xsx3PFoypALOV7R0YNL29jI3F2XkZA8v24wfNvPi0DETcC
ZOxw4G1erIEjjj51Qz4M7okjQecJxPHOJ+Nz6iNZEDFcZG2b15phCRSQKZwSHP+b
Erw6a4NPs1foieZyk260KSOB8lFs9e8bUJfXd4FfA7l60RA9582K6p05aqVtehFW
ONTe8ULv8F0ba+EzVyTodzzY6ehjD+uc31zL6mDFIbiW+InivFbfi2uDVN1BP/US
m99lLHvDEthnkTokFrbDu81kXdD0lHwIu4O0EMzCnw2E0vWi3sGKd+M0P0sv4WA=
=1qxh
-----END PGP SIGNATURE-----
Author Public Key
npub1j3u42vq63qzs2nyddgkf4s4t7pa85x855vas54e6yauxsvpf2wcsacwg9h