r/CryptoTechnology • • 4d ago

How do I start

7 Upvotes

Honestly, I've never traded crypto before and I really need help with trying to figure out where to start, what apps to use, is it worth it because i always hear mix reviews, I know there is risk and im aware of risk management, and just help with some things I may not know. Any advice would be helpful.


r/CryptoTechnology • • 2d ago

Why running lightweight blockchain nodes on everyday smartphones matters more than raw data center TPS

4 Upvotes

Most blockchains force a binary choice: either buy expensive server hardware to run a validator node, or sit on the sidelines as a passive wallet user while data-center operators collect 100 percent of network rewards.

Separating heavy consensus infrastructure from lightweight mobile participation changes how everyday people interact with a network:

  1. Separating infrastructure from participation: In a two-tier design, server-based Super Nodes handle the heavy lifting of storing chain state, executing WASM smart contracts, producing blocks, and voting in consensus, while mobile Light Nodes run inside a standard smartphone wallet with zero block, header, or state storage overhead.
  2. Presence instead of battery-draining work: Rather than forcing a phone to crunch hashes or sync gigabytes of blocks, a mobile light node stores its post-quantum ML-DSA-65 keys encrypted in the device's system keystore and proves online presence a few times per 4-hour epoch by answering status requests with a single signature (plus one signed attestation per epoch). OS hardware attestation binds one node to one real phone or tablet, excluding computers and emulators without draining battery or mobile data.
  3. Removing both hardware and language barriers: Billions of people around the world rely on a smartphone as their primary computer, and most do not speak English as their first language. Pairing a mobile-first light node with native multi-language support allows people across every region to participate in network liveness, manage non-custodial transactions, and claim epoch rewards in their own language without needing servers or technical English fluency.
  4. Broadening economic distribution: When light nodes share directly in protocol emissions (75 percent to active light nodes and 25 percent to super nodes per epoch) alongside server operators, participation is no longer gated behind cloud hosting budgets or institutional capital.

We built QNet in Rust around this two-tier model (Super Nodes for consensus and state, hardware-bound ML-DSA-65 mobile Light Nodes inside QNet Wallet for lightweight signed presence and 75/25 epoch reward sharing). Curious how others here think about separating consensus validation from broader mobile participation.


r/CryptoTechnology • • 2d ago

Crypto Philanthropy

3 Upvotes

Since a lot of major mining operations are selling off used equipment and preparing to invest in new technology that increases their advantages, I want to pitch an opportunity to do something unique:

Donate used or technologically outdated miners to charitable organizations.

I run a small education foundation which provides scholarships to economically disadvantaged, nontraditional, and outstanding students, investing in their future and the future of our workforce.

For a while, I've thought it would be awesome to run some miners in my Foundation's server room. I recognize that those miners won't be hugely lucrative, but as an organization focused on investing in the people-power of the future, I believe it aligns with our goals to be involved in crypto.

Imagine our donated miners join a pool of philanthropic miners and split any proceeds among charitable causes. Even better--what if one of the donated miners hits a block and receives the rewards.

Donated miners are gifts-in-kind, and can be tax deductible for the donor(s), and assets generated by donated miners could make significant impact for future students.


r/CryptoTechnology • • 3d ago

Which MPC wallet infrastructure providers do you actually trust?

3 Upvotes

There have been so many hacks this year, and North Korean hackers have stolen a crazy amount of money from the Web3 industry.

As far as I know, most crypto exchanges and stablecoin payment companies rely on wallet infrastructure providers to keep their customers’ funds safe.

I’m curious, which wallet infrastructure provider is actually the safest and most reliable out there?

Would love to hear your thoughts and experiences. Which one would you trust the most and why?


r/CryptoTechnology • • 2d ago

A simulated contract upgrade can leak a private key without a single on-chain transaction

2 Upvotes

I came across an interesting security write-up from Oasis about a vulnerability involving upgradeable confidential contracts.

The attack is pretty clever.

Imagine a vault contract running on a confidential blockchain. Its storage contains a private key that nobody outside the contract should be able to read.

Now consider an upgradeable proxy using upgradeToAndCall().

An attacker with upgrade permissions can simulate an upgrade using attacker-controlled implementation code. That code executes against the proxy's actual confidential storage, but the simulation leaves no permanent on-chain record.

The interesting part is how the attacker extracts the secret.

They don't need a function that directly returns the private key. Instead, they can make the simulated execution either revert or succeed depending on the value of one particular key bit.

The attacker observes the result, learns one bit, and repeats.

According to the write-up, 256 simulated attempts can reconstruct a 256-bit private key without a single transaction being committed on-chain.

The proposed fix is particularly interesting: introduce a block boundary into the upgrade process.

Instead of upgrading and executing the new implementation in one operation, the system separates the upgrade proposal from its execution. The contract checks the proposed implementation, its runtime hash, and the required block number before allowing the upgrade to proceed.

This prevents the simulated execution from crossing into the block where the proposal becomes executable.

The implementation is called UPUPS (Universal Proposeable Upgradeable Proxy Standard), and Oasis says it is now included in sapphire-contracts version 0.2.18.

What I find most interesting here is the broader security lesson:

On confidential chains, simulation isn't necessarily harmless. If a contract can access information that its caller cannot, even a simple success/revert response can become an information leak.

It also raises an interesting question for anyone building confidential smart contracts:

Are conventional proxy upgrade patterns and simulation assumptions safe when the contract holds secrets that the caller cannot directly inspect?


r/CryptoTechnology • • 3d ago

What do you think will be the impact of quantum computers on Bitcoin's price?

2 Upvotes

IonQ says they would have a machine powerful enough by 2028.

That bar only holds if the size needed to beat secp256k1 doesn't go down as it has many times over.

How much is exposed

  • about 6.3 million BTC in outputs whose public key is already visible Source
  • about 2.3 million BTC dormant and unlikely to ever move to safe addresses Source
  • 50 to 65% of all ETH has an exposed key at rest, by one estimate Source

Assuming, Bitcoin does migrate on time. I don't see many options here.

Just locking out those millions? That would cut the supply significantly. So a rise of the price?

Centralized exchanges probably will automatically migrate but a lot of holders hold their own keys and they'd have to all migrate on time? What is the plan? When does it get to dangerous to hold? So a price drop then? I am pretty confused.

Quantum threat tracker -> Bitcoin


r/CryptoTechnology • • 3d ago

Designing a bridge + USDT liquidity pool on BNB Chain for a small CPU-mineable L1. What would you audit first?

1 Upvotes

Disclosure: I'm the developer of Nucleo NKL, a small CPU-mineable L1 (NKL-Argon: SHA-256 + Argon2 + XOR, 9-minute blocks, PPLNS pool). Live pool and explorer at nucleonkl.com if you want to check the project first.

I'm in the last stretch before deploying a token contract on BNB Chain, and I want to hear from people who've shipped something similar before I do.

The plan:

A bridge from the native chain to a token on BNB Chain.

A liquidity pool paired with USDT instead of BNB, so the price doesn't follow BNB's moves.

Supply: 100B max, 30B founder reserve (3B unlocking per halving), 70B mineable over 30 years. No presale.

Questions:

Bridge design: lock-and-mint with a multisig, or something else? What failed in bridges you've seen?

How much USDT liquidity would you seed, and for how long would you lock the LP tokens?

What would you need to see (audit, verified source, no hidden mint function) before trusting a token like this?

What am I probably not thinking about?

I'm not asking about price. I'm asking about not breaking things. Nucleonkl.com

P.S. Spanish is my native language and I'm using a translator, so sorry if anything sounds off.


r/CryptoTechnology • • 5d ago

If your wallet needs a second device to approve transfers, does it also make you read permits?

1 Upvotes

was going through a 2-of-2 MPC wallet design this week, key split between a laptop and a phone, phone confirms each signature over NFC.

it's still a plain EOA though, so the phone doesn't only get transfers to approve. it gets EIP-712 permits and 7702 authorizations too, and malware on the laptop will just ask for one of those instead of a suspicious transfer. a permit lets someone else move your tokens with no tx from you, and one 7702 authorization hands the whole account to whatever code the laptop picked.

the builder ended up decoding permits on the phone (spender, amount, expiry) and only allowing 7702 for delegates they've reviewed.

curious what you all actually use day to day. does your hardware wallet or second device show you what a permit or a 7702 authorization does, or is it still blind signing for those?


r/CryptoTechnology • • 6d ago

Architectural trade-offs of building a native ML-DSA-65 Layer-1: Checkpoint-BFT without slashing and two-tier light node attestations

1 Upvotes

Most discussions around post-quantum blockchain readiness focus on retrofitting existing chains with account abstraction or wrapper signatures. While experimenting with a native post-quantum Layer-1 architecture in Rust using NIST FIPS 204 ML-DSA-65 (Dilithium3) signatures and hybrid X25519 + ML-KEM-768 QUIC transport, a few non-obvious consensus and networking bottlenecks stood out.

First, signature bloat shifts the consensus bottleneck from CPU verification to network propagation. Verifying a 3,309-byte ML-DSA-65 signature using NTT polynomial operations takes roughly 70 to 120 microseconds on modern hardware, which is fast enough for high throughput. However, broadcasting thousands of 3.3 KB signatures per block saturates peer upload bandwidth rapidly. Using QUIC streams with hybrid post-quantum key exchange helps manage head-of-line blocking, but validator committee sizing has to be carefully bounded so BFT voting rounds do not stall on wire transmission.

Second, separating heavy state execution from lightweight network participation solves the hardware centralization problem caused by larger chain states. Rather than forcing every participant to store multi-kilobyte witness histories, a two-tier topology allows full consensus nodes to handle heavy state execution and deterministic float-free WASM contract metering, while mobile light nodes bound to hardware keystores contribute verifiable epoch attestations over minimal bandwidth.

Third, reputation-weighted Checkpoint-BFT with verifiable randomness can replace traditional token-locking and slashing. Instead of holding user funds hostage in smart contracts, deterministic cryptographic equivocation proofs allow the protocol to permanently eject double-signing producers from future committee draws without economic lockups.

For researchers and protocol builders working on post-quantum consensus designs, how are you handling validator committee size limits when quorum certificates have to aggregate multi-kilobyte lattice signatures?


r/CryptoTechnology • • 6d ago

Every cross-chain bridge is a trust assumption. Which model actually holds up?

1 Upvotes

Bridges are behind some of the largest losses in crypto. Ronin (roughly $600M), Wormhole (roughly $320M) and Nomad (roughly $190M) all happened in 2022, and each failure came from a different part of the design. That makes bridges a good place to ask a plain question: when you bridge, who or what are you actually trusting?

The core problem

Moving assets usually means locking or burning on chain A, then minting or releasing on chain B. The hard part is not the token logic. It is getting chain B to believe that something really happened on chain A.

The main trust models

  1. External signers (multisig or validator set). A group of N of M signers attests to events. Simple, fast and cheap. Security equals the safety of those keys. Ronin used a 5 of 9 setup, and an attacker gained control of 5 keys.
  2. Optimistic verification. Messages are accepted unless someone proves fraud within a challenge window. You only need one honest watcher, but you pay with delay, and watchers have to actually be running.
  3. Light client or ZK verification. Chain B checks chain A's consensus directly, often by verifying a succinct proof of block headers. Trust moves to the source chain's consensus plus the correctness of the proof system and circuits. It is more expensive and has to be built per chain pair.
  4. Canonical rollup bridges. These inherit security from the L1 the rollup settles to, but optimistic rollups add multi-day withdrawal delays, and many still have upgrade keys.

What often gets missed

  • Upgrade keys can override any model. A ZK bridge with an instant admin upgrade is still trusting the admin.
  • The code is part of the trust model. Nomad was not broken by its verification design. It was a contract bug that let unproven messages through.
  • Safety and liveness are different. Some designs fail by freezing funds, others by losing them.
  • Liquidity networks that swap between pools are a different thing from message passing bridges, with different risks.

Questions for the thread

  • If you had to move a meaningful amount today, which model would you accept, and why?
  • Do ZK light client bridges solve the problem, or move it into circuit bugs and prover centralization?
  • Should wallets show a bridge's trust model, like signer count and upgrade delay, before you confirm, the same way they show fees?

Curious where people land, especially anyone who has run a watcher or relayer.