welcome to orb
I EXPLAIN HOW SYSTEMS ACTUALLY WORK — ONE CONCEPT A DAY. WEB3 TODAY, AI NEXT. FOUNDER OF WEB3 EDUCATION HERE ON HEY.
  • 215 FOLLOWERS
  • 220 FOLLOWING
  • MEMBER OF 15 CLUBS
$20 REVENUE ON ORB
Posts

How to Change the Wallet Connected to Your Lens Account (Ownership Transfer)If for any reason you want to change the wallet connected to your Lens account, follow along with me in this post.Warning: please do this carefully and with attention, as you may lose access to your account. You can also see all the steps in the video file.First, open the link below: https://account.fkng.social/dashboardIn this section (photo 1), enter your account's username in the top box.If you've done this correctly, your account will be identified, and in the box below you'll see the wallet you've connected to your account (photo 2).Click "Connect Wallet" and connect to your wallet. You'll then enter your account page (photo 3).In the "Account Owner" section, click "Change Owner" (photo 4).In this box, enter the new address you want to connect to your account in place of the old one. Make sure you have access to the new address, because after this you can only connect to your account with the new wallet address.Click "Confirm Change Owner".While your wallet is still on the old address, confirm the transaction.If everything goes correctly, you should receive this message: "Ownership transferred successfully." (photo 5)Now log out on the same page and log in again.If you succeeded, you can return to hey; and if you see a message asking you to log in again, refresh the page and log in with the new address.Congratulations — you've done it.
With sincere thanks to @namyleusa for the guidance.

27 Reactions4 Replies & Quotes$0.40 Tips

North Korean hackers stole $1.5 billion from Bybit — by making the verification screen itself lie.On February 21, 2025, Bybit — one of the world's largest crypto exchanges — was moving funds in a routine cold-wallet transfer. The signing screen showed the familiar destination. What the contract actually did was hand full control of the wallet to the attacker. Within minutes, roughly 400,000 Ethereum — about $1.5 billion — was gone: the largest crypto theft on record. The FBI attributed the heist to North Korea's Lazarus Group, known as TraderTraitor.The number: about $1.5 billion — nearly 400,000 ETH — moved in minutes, after weeks of preparation.No vault was cracked. The attackers compromised a Safe{Wallet} developer machine and injected malicious JavaScript that acted only when a Bybit signer appeared: it showed the original transaction, swapped the signed payload for a fake one, then restored the display so colleagues saw a normal approval. The signature that everyone verified was attached to the lie.It worked because the verification step itself was captured. Multisig approvals assume the interface tells the truth — and when the thing you check with is the thing that lies, more eyes change nothing.What stops it:Verify transaction details on a second, independent device — not only the screen that asks you to sign.For infrastructure teams: developer machines and build pipelines are production assets — guard them like the vault.Treat any signing interface as code you must audit, especially after vendor-side incidents.For exchanges: rehearse the crisis — Bybit scrambled for liquidity so users could withdraw, but the drill costs days.The bitter part: the blockchain part lasted minutes while the preparation lasted weeks; Bybit covered users, yet the stolen funds entered a months-long laundering chase — and the truth came from forensics, not from any screen.When you confirm a transaction, what are you actually trusting?The screen that verifies can lie.#CyberSecurity #Crypto #SupplyChain #Hacking

4 Reactions0 Replies & Quotes

Why is a blockchain block always full — and why is that considered healthy?Most systems treat capacity as something to maximize. Ethereum treats it as something to meter. A block has a gas limit, and the limit exists not because the hardware cannot do more, but because every node must re-execute every block — and the limit is the promise that "anyone" stays possible.🧩 Ethereum prices two kinds of scarcity in one block. Execution gas covers computation, metered so every node spends the same effort. Data adds a second meter: since EIP-7623, a byte of calldata costs a floor of 10 gas if it is zero and 40 if it is not — priced so that data-hungry transactions cannot hide inside "cheap" execution.🔧 The numbers are bigger than they were. The gas limit was raised to 60 million, and blobs now have their own target and ceiling, each tuned separately from execution. The design is elastic rather than fixed: a target keeps the chain comfortably full, a ceiling absorbs spikes, and the base fee moves between them to keep the market honest.💡 What I find fascinating about this: a full block is not congestion — it is the system working. If blocks were routinely half-empty, the pricing was too high and users were overpaying. "Full" is the signal that the market found the price.✅ The second consequence: raising the limit is not free, and it is not a settings change. It is a governance vote, because a bigger limit raises the hardware floor for every node — and the moment "anyone can verify" quietly becomes "anyone with a server", the chain has traded its soul for throughput.⚠️ Trade-off is real: the floor pricing on calldata pushes data-hungry users toward blobs, which is intended — but it also makes small data postings more expensive for ordinary apps, which complain loudly. Every capacity decision picks a winner.The honest summary: a block limit is not a bottleneck to remove. It is the boundary of decentralization, priced and defended.The infographic below 👇 gives a quick visual if you're new to blockspace.#Ethereum #Scaling #Blockspace

5 Reactions2 Replies & Quotes$0.10 Tips

The U.S. charged a ring that enrolled "ghost students" with stolen identities — and used super intelligence to do their coursework.Since about 2021, conspirators have used stolen American identities to submit fraudulent FAFSA applications, enrolling "ghost students" at community colleges and universities across the country. The fake students never attend; the loan and grant money arrives, and the refunds flow to bank accounts controlled by foreign actors, moved by U.S.-based money mules who keep a cut. This month, the Justice Department unveiled indictments in two states and charged five defendants — and said fraudsters even use super intelligence to complete required coursework so the ghosts stay enrolled.The scale: more than $32,000,000 in identified losses, 830,840 potentially fraudulent student-aid IDs tied to nearly $130,000,000 — and an overall estimate the department puts well above $200,000,000.The scam needs no hacking. A stolen name, date of birth and Social Security number are enough to open a FAFSA account; aid is disbursed to the school, the "student" never shows up, and the leftover refund is the payout. Enrollment itself becomes the theft.It worked because colleges count head count, not presence: a name on the roster is treated as a person, and online classes make attendance nearly unverifiable.What stops it:Colleges: verify identity at enrollment and flag students who never engage with coursework.Students and parents: check your studentaid. gov account for FAFSA applications you never filed.Treat unexpected aid refunds as an alarm — they may be the payout of a ghost in your name.Report suspected identity misuse to the Education Department's inspector general early.The bitter part: the scheme has run since at least 2021 and indictments landed only this fall; officials seized $750,000 in cryptocurrency in Kenya — a first of its kind — while the estimated scale keeps climbing past $200 million.Would your college notice if "you" never logged in?An enrolled name is not proof of a student.#CyberSecurity #IdentityTheft #FinancialAid #Fraud

6 Reactions0 Replies & Quotes

Why does storing a file on a blockchain cost almost nothing — and proving it costs a fortune?Renting a terabyte from a cloud provider runs about $23 a month. The raw disk is a commodity. What you are actually paying for is an SLA: the provider's promise that the bytes are intact, reachable, and will stay that way.Filecoin turned that promise into a market — and made the promise the expensive part.🧩 Storage providers compete on price to hold data, and the raw cost of that storage is low because disk is a commodity everywhere. The expensive part is proof. Every provider must regularly demonstrate — through cryptographic proofs, on-chain, on a schedule — that the data is still there and intact.🔧 Proof is not a one-time event. Providers "seal" data into sectors, a costly computation, then prove that the sealed data exists, continuously, for the life of the deal. Fail a proof and you are penalized. That continuous proof-of-storage is what makes the guarantee expensive — and it is why the raw storage price can stay low while the total cost of a deal is much higher.💡 What I find fascinating about this: the cloud hides the guarantee inside the price, so nobody sees it as a separate product. Filecoin unbundles it. You can see exactly what "the data is still there" costs, because someone is bidding on it, every day, in the open.✅ The practical consequence: cheap storage with a real guarantee enables use cases cloud pricing cannot touch — archival data, scientific datasets, long-tail content that would be uneconomical on standard cloud tiers.⚠️ Trade-off is real: unbundled guarantees are only as good as the market's depth. If few providers compete for your data, the price may not be low, and the guarantee may not be as robust as a hyperscaler's. Decentralization helps, but it is not free.The honest summary: space has always been cheap. What is expensive is someone taking responsibility for it, on a schedule, in public.The infographic below 👇 gives a quick visual if you're new to decentralized storage.#Filecoin #Storage #Web3

8 Reactions0 Replies & Quotes

A ring spent more than a year defeating every check a bank makes — aiming at $373,000,000 sitting in 3,000 accounts.Federal prosecutors in Texas unsealed a 22-count indictment against fourteen defendants — including, allegedly, corrupt insiders at major banks and telecom carriers. From July 2023 to November 2024, they allegedly collected personal data, manufactured counterfeit ID documents, impersonated victims, spoofed and SIM-swapped phone lines, intercepted security codes, and used those insiders to bypass authentication at Truist, Bank of America, JPMorgan Chase, Charles Schwab and other banks. Among the plays: an attempted $2,000,000 wire abroad.The prize: a spreadsheet of nearly 3,000 victims whose accounts together held over $373,000,000 — the number prosecutors cite for what was at stake, not what was confirmed taken.The design was layered. A stolen name was not enough; the ring printed IDs that could pass a teller, moved victims' phone numbers so security codes arrived on their own SIM, and bought bank and carrier employees to wave the rest through.It worked because verification is a chain — and one purchased link breaks every check behind it. A passed check was the product.What stops it:Set account alerts and a credit freeze; takeover rings start from data you cannot see being used.If your phone loses service without explanation, treat it as a SIM swap and call your carrier from another device.For institutions: log and review every manual authentication override — bought insiders are the weakest link.Move large wires only through a channel you initiate, with a cool-off period on your side.The bitter part: the indictment is an allegation, but the flight was real — the accused ringleader was arrested at the JFK gate, boarding a one-way flight to Malaysia with his family's possessions already shipped to Kenya.If your bank said everything looked normal, what would you still check?A passed check is not proof of identity.#CyberSecurity #IdentityTheft #BankFraud #SocialEngineering

5 Reactions0 Replies & Quotes

Why does staking more ETH pay each staker less — and is that a bug or the point?On most systems, more participation means more revenue to share. Ethereum runs the other way on purpose. Right now, with roughly a third of all ETH staked, validators earn about 2.6% a year — and that number is designed to fall as more people join.🧩 The reward per validator is proportional to its own stake and inversely proportional to the square root of the total ETH staked. That square root is the whole story: if staked ETH doubles, the network's total issuance grows by about 41%, so the return on each staked ETH drops by roughly the same amount. Issuance rises, but yield falls — deliberately.🔧 The curve has an economic logic. Ethereum does not want validators "because staking is profitable"; it wants just enough validators to make the chain expensive to attack, and not one more than necessary. A falling yield is a thermostat: it attracts participation when security is thin and cools the market when it is thick. Proposals like EIP-8361 push this further, tapering rewards toward zero as staking approaches half the supply.💡 What I find fascinating about this: the thermostat is currently reading warm. At ~33% staked and ~2.6% yield, Ethereum sits between "not enough security" and "oversaturated staking" — and the entire discussion about MEV rewards and EIP-8361 is about what to do when the thermostat is no longer enough.✅ The practical consequence: your staking return is set by everyone else's decision, not by your own. When yield falls, it is not that you are earning less — it is that the job is being divided among more people.⚠️ Trade-off is real: a falling yield makes solo staking less attractive while fixed costs stay flat, which quietly pushes stakers toward pooled operators and centralized providers. The curve protects the protocol's budget at the cost of concentrating its operators.The honest summary: Ethereum does not price staking by what it costs to run a validator. It prices it by how many people Ethereum needs to be safe.The infographic below 👇 gives a quick visual if you're new to staking economics.#Ethereum #Staking #Tokenomics

5 Reactions0 Replies & Quotes

Desktop wallets vs browser-extension wallets — which is actually safer?Short answer: the installed (desktop) app is generally the safer of the two. Here's why the gap exists. 👇🔓 Where extension wallets are exposedThey live INSIDE your browser — a network-heavy environment with a huge attack surface. Your private key sits in the browser's memory, shared with everything the browser runs: malicious scripts on websites, other buggy extensions, browser vulnerabilities themselves.The most common threats are fake extensions impersonating real wallets, and supply-chain attacks. This isn't theoretical: in December 2025, a compromised Trust Wallet extension update (v2.68) drained roughly $7M from thousands of wallets. Researchers have also documented 150+ malicious fake-wallet add-ons, and a 2026 study found 85 popular wallet extensions with privacy flaws that leak address data and let users be tracked.🛡 Where desktop wallets are strongerThey run as an independent app, protected by the operating system's sandbox. Keys can live in system-level secure storage (like Keychain) instead of browser memory. Updates come straight from the developer — no third-party store in the middle — and the attack surface is far smaller and controllable.Main remaining risks: malware on your computer (keyloggers, clipboard hijackers) and malicious DApps sending deceptive signing requests.📌 If you must use an extensionInstall ONLY from the official store or the project's own website — never through search ads or third-party links.Regularly review your "connected sites" and revoke permissions you no longer use — some wallets don't fully revoke on disconnect.For large transactions, pair the extension with a hardware wallet: the extension only displays, the actual signing happens on the device, and your private key never touches the browser.💡 The bottom lineDesktop or extension, any software wallet is still a HOT wallet — keys on an internet-connected device. For long-term, high-value holdings, the most secure answer is always a hardware (cold) wallet that keeps the private key offline. Treat your software wallet like a daily spending account: only what you can afford to lose.💬 Which do you use — extension or desktop? Comment below
📌 Save this & send it to someone who keeps crypto in a browser extension 🔗#Crypto #CryptoSecurity #HardwareWallet #MetaMask #TrustWallet #Web3 #DigitalSecurity

17 Reactions2 Replies & Quotes$0.50 Tips

For two years, "IntelBroker" sold stolen data on a cybercrime forum — until an indictment named the man behind the alias: Kai West, 25, of Britain.Federal prosecutors in Manhattan unsealed charges saying West and his online group took data from more than 40 victims between 2023 and 2025: a telecommunications company, an internet provider, and a municipal health care provider whose patient files held names, Social Security numbers and dates of birth. On a hacking forum, the alias listed the loot 158 times — at least 41 posts selling data, the rest given away free or for forum credit to build a reputation. Prosecutors say at least $2 million was sought; the sixteen listings with explicit prices alone top $2.4 million. Payment: Monero.The damage: at least $25,000,000 across the victims — while the sales were only the storefront.He did not breach everyone himself. He led a group, listed what others stole, priced it or gave it away, and let the marketplace do the rest. One victim's records came from a single misconfigured server — a listing waiting to happen.It worked because stolen data is a currency: one breach can be resold forever, and a seller's reputation made buyers trust the goods — the alias was even named a forum "owner."What stops it:Treat every breach as a marketplace event: assume the data will be resold, not just leaked.Audit exposure, not just perimeters — a misconfigured server is a listing waiting to happen.Never treat crypto as invisibility; the payment trail became part of the case.If your data appears for sale, report it — those forum posts became the evidence.The bitter part: West was arrested in France in February 2025, the United States is still seeking extradition, and what he posted became the evidence.If your records were listed on a forum, how would you ever find out?An online alias is not an alibi.#CyberSecurity #DataBreach #CyberCrime #IdentityTheft

8 Reactions0 Replies & Quotes$0.05 Tips

How does a chain check a million signatures in the space of one?Ethereum runs on roughly a million validator signatures per day. Every attestation has to be stored, transmitted, and checked. If each signature were counted the way Bitcoin counts them, the chain would spend its capacity just proving that people agree. It does not — because of one property of one curve.(This revisits BLS aggregation from September — that post covered what it is. This one covers why it scales.)🧩 BLS signatures are points on the BLS12-381 curve, and points on elliptic curves can be added. Adding two signatures produces another valid signature on the combined message. That is the entire trick: aggregation is just curve addition, so any number of signatures over the same message collapse into one, and one pairing check verifies the whole group at once.🔧 The numbers explain the design. A BLS12-381 signature is 48 bytes — the same size whether it comes from one signer or from every validator in a committee. Committees of 128 attest, their signatures collapse into one, and slot after slot the chain stores proofs of consensus that scale linearly in cost, not in signers.💡 What I find fascinating about this: the same curve that makes Ethereum cheap makes it manipulable in a small, known way. Because anyone can aggregate, a malicious aggregator can also suppress signatures — leaving out a validator from the bundle it relays. Aggregation is free mathematically, but the aggregation service is a trust question, and Ethereum keeps redesigning around it.✅ The practical consequence reaches beyond consensus: the same curve powers EIP-7998, which proposes turning the RANDAO reveal into a BLS-based VRF — reusing one cryptographic primitive to fix a different weakness.⚠️ Trade-off is real: BLS verification is slower and heavier than ECDSA per signature, and aggregation requires proof-of-possession to prevent key-cancellation attacks. The curve chose throughput over everything else, deliberately.The honest summary: BLS does not make signatures smaller. It makes their number irrelevant — and consensus without that property was never affordable.The infographic below 👇 gives a quick visual if you're new to BLS signatures.#Ethereum #BLS #Cryptography

22 Reactions0 Replies & Quotes