Johnny Lim (Woojong Lim) [email protected]

3.7K posts

Johnny Lim (Woojong Lim) neolha@handcash.io banner
Johnny Lim (Woojong Lim) neolha@handcash.io

Johnny Lim (Woojong Lim) [email protected]

@neolha

$neolha, https://t.co/bymLLUPu2W father, developer, architect BSV Association Ambassador for Korea I may judge your actions, but never you.

대한민국 성남시 Katılım Ocak 2010
391 Takip Edilen596 Takipçiler
Johnny Lim (Woojong Lim) neolha@handcash.io
3개의 문(A,B,C)이 있고 그 중 하나의 뒤에는 거액의 상금이 놓여있다. 당신이 A 를 선택하자 상금이 어디 있는지 알고 있는 진행자가 세번째 문 C를 열어 C에는 상금이 없다는 것을 보여준뒤 '자 이제 당신의 선택을 바꾸시겠습니까?' 라고 묻는다면? 1. 바꾼다 2. 안 바꾼다 youtu.be/IophSL7U01U?si…
YouTube video
YouTube
한국어
0
0
0
45
Johnny Lim (Woojong Lim) neolha@handcash.io
BRC-100지갑에 레가시 주소 지원이 안되는 게 오류가 아니라는 것을 이해하는게 정말 중요함
Hodos Browser@HodosBrowser

@Brendan_Lee__ you're not stupid. Every BSV user hits this, and most quit right here. BRC-100 doesn't expose a legacy-style receive address. Exchanges don't support BRC-100. Most BSV funds live in legacy wallets — @handcashapp, @ElectrumSV, @rockwallet — and there's no direct path from any of them to a BRC-100 wallet. That's where people give up and wrongly blame the protocol. The friction is a UX gap, not a protocol problem. @DevelopingZack has it right — funding should be as simple as 1, 2, 3: download, setup, fund. @deggen added legacy receive to BSV Browser to help close that gap. Hodos chose to put legacy + BRC-100 in one wallet, side by side in the same app — because the transition needs a bridge. Same philosophy as the browser itself: Hodos Browser bridges Web2 to Web3, Hodos Wallet bridges legacy to BRC-100. Users do need to install a new browser, but Web3 will eventually need full control of the browser layer. Why not get a head start? Credit to @ProjectBabbage and @BSVAssociation for the BRC-100 standards that make this possible. Hodos is independent of both Babbage and the BSVA, we built directly from the public standards — and it interoperates with BRC-100 apps from any independent dev anywhere, like @johncalhooon, with zero coordination required. That's what an open standard looks like in practice. Public beta is live today — HodosBrowser.com

한국어
0
1
2
135
Hodos Browser
Hodos Browser@HodosBrowser·
@Brendan_Lee__ you're not stupid. Every BSV user hits this, and most quit right here. BRC-100 doesn't expose a legacy-style receive address. Exchanges don't support BRC-100. Most BSV funds live in legacy wallets — @handcashapp, @ElectrumSV, @rockwallet — and there's no direct path from any of them to a BRC-100 wallet. That's where people give up and wrongly blame the protocol. The friction is a UX gap, not a protocol problem. @DevelopingZack has it right — funding should be as simple as 1, 2, 3: download, setup, fund. @deggen added legacy receive to BSV Browser to help close that gap. Hodos chose to put legacy + BRC-100 in one wallet, side by side in the same app — because the transition needs a bridge. Same philosophy as the browser itself: Hodos Browser bridges Web2 to Web3, Hodos Wallet bridges legacy to BRC-100. Users do need to install a new browser, but Web3 will eventually need full control of the browser layer. Why not get a head start? Credit to @ProjectBabbage and @BSVAssociation for the BRC-100 standards that make this possible. Hodos is independent of both Babbage and the BSVA, we built directly from the public standards — and it interoperates with BRC-100 apps from any independent dev anywhere, like @johncalhooon, with zero coordination required. That's what an open standard looks like in practice. Public beta is live today — HodosBrowser.com
Brendan Lee@Brendan_Lee__

How does one get a receiving address out of the Metanet desktop app? Am I stupid or is it just impossibly obtuse?

English
4
6
26
1.7K
Johnny Lim (Woojong Lim) [email protected] retweetledi
Ry4N was here 🐉
Ry4N was here 🐉@imablackwolf·
We just went through Teranode's source code on GitHub. What we found changes how we think about BSV's entire network layer. Start with the DNS seeds. SV Node ships 6 hardcoded seeds for peer discovery. We queried all 6 tonight. Two domains don't exist. Two resolve but return nothing. Total peers from the entire official discovery infrastructure: 5. So we asked the obvious question — is SV Node being sunset? Opened up the Teranode repo and found three networking layers: P2P service — new libp2p protocol with DHT discovery and gossip propagation. Teranode-to-Teranode only. Propagation service — HTTP endpoints for tx submission. This is what Arcade and apps already use today. Legacy service — the old Bitcoin wire protocol. Contains peer management, connection manager, address manager, netsync. Everything SV Node does. They named the folder "legacy." The Bitcoin P2P wire protocol isn't dead. It lives on inside Teranode. But they literally labeled it legacy. The future is libp2p between Teranodes and HTTP propagation for everyone else. Here's the gap: Teranode solves miner-to-miner. It does not solve app-to-blockchain. Nobody is building a Rails app and spinning up Teranode. Nobody wants to manage raw tx hex, UTXO sets, and SPV proofs from scratch. That's the layer we built. The Indelible Federation sits between Teranode and your app. Teranode is the highway. Our bridges are the off-ramps. Apps call spvFetch() and everything works. Here's exactly how the bridge adapts: Right now each bridge has two sides — P2P sockets talking to BSV nodes on one side, HTTP APIs serving apps on the other. Transactions flow in from P2P, get verified, get served to apps. We're adding Teranode's propagation endpoint as a third tx source. The bridge will POST transactions to Teranode for broadcast instead of pushing inv messages to 4 peers and hoping they propagate. It will pull new transactions from Teranode over HTTP instead of waiting for P2P inv announcements. Same SPV verification. Same app-facing API. The app doesn't know or care where the transaction came from. P2P stays as a fallback. If Teranode's endpoint goes down, the bridge falls back to wire protocol peers automatically. If legacy P2P sunsets entirely, the bridges already mesh with each other over the federation network. Three layers of redundancy: Teranode HTTP, legacy P2P, federation mesh. No migration. No breaking changes. The bridge just gets a faster, more reliable tx source while keeping every fallback it already has. #BSV github.com/zcoolz/relay-f… Five DNS peers. Two dead domains. A wire protocol moving to legacy status. And an app layer that still needs someone to solve the last mile. We read the source. We're building for what comes next.
English
6
10
55
2.6K
Johnny Lim (Woojong Lim) [email protected] retweetledi
Jorge Pelaez | BSV COL
Jorge Pelaez | BSV COL@BitcoinSVCOL·
In 2015, when Dr. CSW mentioned that he privately owned one of the world's top 100 supercomputers—with computing power just 3% less than that of the NSA—no one in the Bitcoin world believed him. Yet here is the evidence proving he was telling the truth. Ironically, the article most cited by other scientists on SSRN is "Investigation of the Potential for Using the Bitcoin Blockchain as the World's Primary Infrastructure for Internet Commerce" the one he produced using this supercomputer, rather than the Bitcoin white paper. papers.ssrn.com/sol3/papers.cf… The truth is right there, in plain sight for anyone with eyes to see it: @CsTominaga is Satoshi Nakamoto. youtu.be/Sne292YHu5k?si…
YouTube video
YouTube
Jorge Pelaez | BSV COL tweet mediaJorge Pelaez | BSV COL tweet media
MrBen@71Nous

@CsTominaga the Hayekian economist with a computer science degree with the necessary hardware who built the thing Hayek could only theorize about.

English
20
59
190
10.9K
Johnny Lim (Woojong Lim) neolha@handcash.io
Ry4N was here 🐉@imablackwolf

Built a 12-agent BSV task swarm for the BSV Association Open Run hackathon. Task broker, BRC-100 wallets, x402 payments, Merkle proof system, live dashboard, worker threads, federation bridges. All working. Real transactions on-chain right now. I'm not submitting. Here's why. The hackathon requires "at least 1.5M meaningful on-chain transactions within a designated 24-hour window." The website never says when that window is. Not on the timeline. Not in the rules. Not in the announcements. It just says "designated" without designating it. The only place it was ever clarified was a Discord thread on April 14, where a participant asked "Sounds like we have 72 hours now to generate 1.5 million instead of 24? Is that correct?" and the organizer confirmed April 14-16. That was it. No announcement. No email. No update to the website. Just a reply buried in a thread. Meanwhile on the same Discord: Multiple participants asked how to submit and were unsure of the process The transaction window was changed from 24 hours to 72 hours mid-hackathon with no formal announcement Participants asked about broadcast endpoints and rate limits and were told to "scroll up" for instructions One builder's PC restarted overnight and lost his run — because there was no warning that the window was already active The website still says "24-hour window" while Discord says 72 hours I spent April 14-17 diagnosing and fixing SDK bottlenecks — createAction takes 1000ms due to 8 sequential SQLite operations, synchronous better-sqlite3 blocks the event loop, UTXO fragmentation requires manual splitting, the Monitor throws unrecoverable errors on failed transactions. These are real engineering problems that take days to solve. I thought I had time because the rules never said I didn't. The system works. The code is public. The transactions are on-chain. I told people I was going to submit and I couldn't — not because I can't build it, but because I didn't know the deadline I was actually working against. If hackathons are going to require infrastructure-scale transaction throughput, the rules need to be on the website, not in Discord replies. Every participant deserves the same information at the same time.

QHT
0
0
1
131
Johnny Lim (Woojong Lim) neolha@handcash.io
Great work
Ry4N was here 🐉@imablackwolf

When a BSV node starts for the first time, it has no idea who else is on the network. DNS seeds are the phone book — the node asks "who's out there?" and gets back IP addresses of real nodes to connect to. Without working seeds, a new node sits there with 0 connections. Can't sync blocks, can't relay transactions. Dead on arrival. BSV's official DNS seeds have been dying off. The fewer working seeds, the harder it is for anyone new to join the network. We built a replacement. seed.indelible.one crawls the entire BSV P2P network every 5 minutes, handshakes with every node to verify it's real BSV (not BCH), tracks uptime and latency, and serves verified-good IPs via standard DNS. Who is this for: Node operators who need reliable peer discovery Wallet developers connecting directly to BSV Anyone building apps that talk to the P2P network The BSV ecosystem — more working seeds = easier for new nodes to join How to use it: Add to your bitcoin.conf: dnsseed=seed.indelible.one Or query it directly: dig seed.indelible.one Or use the API: curl seed.indelible.one/api/peers Your node gets a fresh list of verified peers every time it starts. No more failed bootstraps, no more stale peer lists. Open source, free forever, running on the Indelible Federation — 6 VPS across the US. github.com/zcoolz/relay-f…

English
1
0
4
128
Johnny Lim (Woojong Lim) neolha@handcash.io
The Bitcoin they worship is no longer the Bitcoin you dreamed of. Your vision still lives on under another name, so perhaps all they ever hijacked was the name. Now that polluted name may be doing more to hold your vision back than to preserve it. Why not let go of the attachment to the name?
English
0
0
2
49
Caffè Satoshi
Caffè Satoshi@CaffeSatoshi·
Satoshi's mask is finally breaking... The Paul Le Roux theory suggests that Satoshi Nakamoto could be a highly skilled programmer who later became a major criminal mastermind. Le Roux built early encryption software (E4M) and had strong cryptographic knowledge that could plausibly match Bitcoin’s technical foundations. He also ran a global criminal empire that required a private, untraceable financial system, which Bitcoin would have perfectly solved for him. to Overlaps in timing, secrecy, personality traits, and his use of multiple identities as indirect alignment with Satoshi’s behaviour and disappearance. No information exists about his incarceration location, many speculate he is under US Government protection instead. Full article 👇 x.com/CaffeSatoshi/s…
Caffè Satoshi tweet media
English
14
1
7
3.7K
The Byzantine General Project
The Byzantine General Project@satoshireveal·
Think about the cognitive dissonance. The same industry that calls Craig Wright a fraud also spent 10 years and millions of dollars fighting him in court. If he's nobody, why not just ignore him? What exactly were they afraid he might prove?
The Byzantine General Project tweet media
English
1
4
36
934
Johnny Lim (Woojong Lim) [email protected] retweetledi
Deggen
Deggen@deggen·
Crew, we're doing it. You're commenting publicly about the software. We're doing our best to make it better based on your feedback. It's taking time but we're getting there. Thank you for your support. v2.2.2 out now desktop.bsvb.tech Existing users will get a ping in a few hours. If you want it NOW just go to: Settings => Check For Updates
English
10
24
136
4.7K
Johnny Lim (Woojong Lim) neolha@handcash.io
집중되어 있는 권력의 폐해를 목도한 대부분의 사람들은 탈중앙화를 통해 권력을 고르게 분산할 수 있다는 발상이 너무나 매력적이었을 것이다. 실제로 기득권으로 부터 뺏어온 권력은 새로운 방식으로 재 분배 되었다. 한동안 모든게 좋았다. 그런데 누군가 갑자기 나타나 탈중앙화는 권력의 고른 분배가 아니라 권력의 제거 그 자체라고 이야기하자, 사람들은 불편해했다. 특히 권력의 공백 그자체가 아니라 많게든 적게든 권력을 나눠 갖고자 했던 이들에겐 그의 이야기가 자신의 선량했던 의도조차 부정당하는 느낌이었을 것이다. 그래서 사람들은 사토시를 십자가에 못박아 버린것일지도. 사람들은 진정 자신들이 무슨일을 했는지 모를까?
한국어
1
2
9
156