r/CryptoTechnology 3d ago

Should users ever need to know your app is built on crypto?

22 Upvotes

A lot of crypto apps make you deal with the infrastructure before you even get to the product.

Connect a wallet, switch networks, sign something, figure out gas, then you can finally use the thing you came for.

Why not just hide all of that unless the user needs it?

If blockchain is infrastructure, the average user probably shouldn’t have to understand what’s happening underneath just to use an app. Do you think hiding the crypto layer is the better path for adoption, or should users know when they’re interacting with something onchain?


r/CryptoTechnology 1d ago

Can a crypto payment system really be called self-custodial if its contracts retain privileged access?

13 Upvotes

The recent Avici exploit reportedly drained more than $653K from card collateral vaults.

The bigger question: if a smart contract has administrative permissions or another privileged path capable of moving user funds, is the system still truly self-custodial? The exact exploit mechanism hasn’t been officially confirmed but it raises an important question about the gap between “self-custody” as a product promise and the underlying architecture.

Where should we draw the line???


r/CryptoTechnology 6d ago

The utility of Ethereum to our bank

5 Upvotes

Full disclosure: I work at N3XT (a chartered US bank) and wrote both of these.

Wrote some articles that I hope causes readers to think more about the real utility of public blockchains and specifically Ethereum. Happy to post links to articles but the post will get autorm'd can drop in comments if people are interested

The first piece highlights the subtle, perhaps largely unrealized, benefit for a bank to use an open standard, on a decentralized public utility as a way to benefit its clients, itself, and Ethereum

Second is a thought experiment pricing what it would cost to run our entire bank ledger on public Ethereum L1 vs a private chain vs a traditional banking core for a $10B bank:

* Legacy core: ~$149k/mo ($0.59/tx)
* Public Ethereum L1: ~$36k/mo ($0.14/tx)
* Private Ethereum: ~$31k/mo ($0.12/tx)

TL;DR

A traditional core is the most expensive way to run our ledger at every size we modeled, and not by a little. That gap never closes anywhere on the curve, which should tell you nobody buys a core for the price.‍

Between public and private blockchains, it's close at our scale and a landslide above it. We model Ethereum L1 directly, not Layer 2s, because rollups do not yet match the decentralization, censorship resistance, or sovereign consensus of mainnet. At Regional bank level, private wins by 13% and the entire margin is less than a quarter of an engineer’s salary. Move our staffing assumption from 0.75 FTE to 1.0 and public wins instead. But at Money Center bank level private wins by 83%, because gas and signing are metered and a private fleet isn't. Every transaction you add is free on one and billed on the other.

The tiebreaker is time. Gas is the only input in this model that gets cheaper, falling somewhere between 20% and 64% a year depending on whether you trust the published Ethereum roadmap or the last five years of history. Everything else moves the other way. Salaries rise, vendor contracts renew upward, and nobody's core gets cheaper at renewal.

Ethereum set out to be a "world computer." As throughput climbs and execution costs continue to collapse, you can start to see a future where public rails displace both legacy core vendors and private cloud fleets alike. That was the original promise of cloud computing: paying strictly and exclusively for what you actually use. Cloud platforms and core vendors answer to shareholders who demand expanding margins, annual price escalators, and locked-in enterprise minimums. Ethereum’s incentive is structurally aligned in reverse: driving unit execution costs down to maximize volume and global network adoption. It becomes the true realization of pay-as-you-go utility computing.

Of course, cost is only one hurdle: public rails still require lower latency and privacy before an institutional bank can migrate live customer ledgers. But on cost alone, we'd have been fine starting on public rails, and we'd probably be better off there within five years. We didn't rent the ledger, but we may yet.


r/CryptoTechnology 19h ago

Is MiCA changing who you work with?

3 Upvotes

Any advice would be of great help, please suggest for the same. This question has been lingering for a while with no means to ascertain except for asking here on Reddit. If any founders, CFOs, developers and affiliates could chime in, then I’d get a better idea. Thanks.


r/CryptoTechnology 1d ago

Why do people in emerging markets actually prefer stablecoins?

3 Upvotes

Stablecoins are becoming quite popular in developing nations, and that is no idle talk. They allow individuals from high-inflation or regulated economies to store dollar value without an American bank account. Also, they are more affordable and quicker compared to the existing remittance services for international transactions. In nations lacking advanced banking system infrastructure, having a stablecoin wallet may be easier to obtain than a savings account. Wondering how much of this comes from necessity rather than convenience, so What do you think?


r/CryptoTechnology 2d ago

Built a cryptocurrency that races against real time instead of hashes, then spent a week trying to prove myself wrong about it

3 Upvotes

LapseCoin is a peer-to-peer cryptocurrency using a Verifiable Delay Function instead of proof-of-work: block production is a race to finish a sequential computation tied to real elapsed time, not a race for a lucky hash. The reason that's interesting: the measured hardware-advantage gap is much smaller than PoW's (roughly 3-10x from Chia's own 2019 hardware competition on the same construction, versus the 10,000x+ ASICs opened up over commodity hardware), so it doesn't push toward the same energy-spiral PoW did. No premine, fair launch, FALCON-512 signatures for the quantum-resistance angle.

Spent the last week trying to actually break my own design instead of just shipping it. Found and fixed a real bug that was silently crashing part of the test suite, pulled real chain data off my own live node to calibrate assumptions instead of guessing, and went after a threat I originally thought was a real gap: whether one operator running many builder addresses could gain an unfair edge over the network. Turned out, once actually simulated instead of assumed, it barely holds up as a problem at all: running many addresses at the same hardware tier wins exactly proportionally, and splitting one machine's throughput across addresses is worse than running it as one. Neither needed a fix.

Whitepaper: https://github.com/Vic-Nas/lapsecoin/blob/main/docs/whitepaper.md
Code: https://github.com/Vic-Nas/lapsecoin

More interested in someone finding a real problem than in users right now. If something in there looks wrong, say so.


r/CryptoTechnology 6d ago

Best way to accept crypto payments from card-buying customers (mobile-first, first-time crypto users)?

3 Upvotes

Building a small web product where standard card payment gateways aren't available to me, so I'm looking into accepting crypto instead. Two flows I'd prefer, in order (if possible); if there's another way, please let me know:

  1. Direct card-to-crypto: Customer clicks Pay on my checkout, gets taken to a service where they pay by card (or however they want), and I receive crypto directly, with no separate step for them.
  2. Stablecoin without gas hassle: Customer buys a stablecoin elsewhere, comes back to my checkout to pay, and doesn't need to hold a separate coin for network fees.

A few constraints:

  • No app download required on the customer's end, needs to work fully in-browser on mobile.
  • If I have to register as a merchant somewhere, it needs to actually support Morocco.
  • Order tracking and automatic fulfillment: after the user pays, I want to know who paid for what so orders get fulfilled automatically.

Has anyone found something that fits this? Open to hearing what's worked (or hasn't) for you.
Thank you so much.


r/CryptoTechnology 14h ago

Which crypto/fiat payment provider handles compliance and doesnt freeze any operation?

2 Upvotes

Trade PS PP just blocked our acc without any reasons. How do you know which crypto-fiat payment provider is trustworthy? In the past I used to choose crypto-fiat payment providers looking only at their marketing page, but it appears to be not enough. What criteria do you use in general when comparing different crypto-fiat payment providers? And have any of you already worked with Inxy, and how was your experience?


r/CryptoTechnology 17h ago

Could programmable Private Keys be the next big thing in crypto?

2 Upvotes

Hi!

I had a revelation for a better way to encrypt Cryptocurrency & it goes like this.... Suppose there is a brand new blockchain designed like many others (Bitcoin for example). If the user was able to program customizable inputs into the Private Key (Linked to it's Public Key or Address) then a user for example could do things such as lock their crypto to that Address until it is unlocked using a secondary password. This would make the currency much safer.

I believe if Bitcoin had these features of customization for it's users wealth it would allow many people (think whales, hodler's, cypher geeks, etc.) to be more safe in these markets!

Any chains currently allow for User end development onto the Blockchain through programming, customization or optimization? TIA!


r/CryptoTechnology 4d ago

How much of a token's behavior should still be upgradeable after users already hold it?

2 Upvotes

Imagine a token behind an upgradeable proxy.

Users acquire it under a set of rules for transfer and redemption. Months later, the implementation is upgraded. Their balances and the token address remain unchanged, but the new version introduces an allowlist for transfers and redeemability.

Bug fixes are an obvious reason to keep the implementation upgradeable. However, I’m less sure whether user-facing rules should be subject to the same upgrade process.

For those who have built upgradeable contracts, where do you draw the line?

Which behaviours should be changeable in place and which should require a new contract or an explicit migration?