KBW에서 나와 같은 주제에 관심 있는 사람을 찾을 수 있다면 어떨까요? 행사에서 많은 사람을 만나지만, 누가 어떤 일을 하고 무엇에 관심이 있는지는 대화를 나누기 전까지 알기 어렵습니다. 가까운 곳에 협업할 만한 사람이 있어도 서로 모르고 지나치기도 하고요. 이런 만남에 도움이 될 수 있도록 Nearby를 만들고 있습니다. Nearby는 관심 키워드를 통해 주변 사람을 발견하는 앱입니다. AI Agent, Payments, DeFi, RWA처럼 관심 있는 주제를 등록하면, 같은 키워드를 가진 사람이 지도에서 먼저 눈에 띕니다. 공통 관심사를 계기로 대화를 시작하고, 커피 한 잔을 나누거나 함께할 사업을 이야기해 볼 수 있습니다. 지갑으로 로그인할 수 있고, 위치는 정확한 좌표 대신 대략적인 구역으로 공유됩니다. 실제로 만난 뒤에는 서로 인증해 만남을 블록체인에 기록할 수도 있습니다. KBW 기간, 관심 키워드를 등록하고 주변을 둘러보세요. 이야기 나눌 동료나 새로운 사업 파트너가 가까이 있을지도 모릅니다. 현재 Injective 테스트넷에서 운영 중입니다. 직접 사용해 보시고 의견 주시면 좋겠습니다. @kbwofficial @injective @NinjaLabsKR

Who’s nearby at KBW—and what are they working on? You meet plenty of people at events, but it’s hard to know who shares your interests until you start talking. Someone you’d love to collaborate with might be just around the corner. That’s why I’m building Nearby. Nearby helps you discover people around you through shared interests. Add keywords like AI Agents, Payments, DeFi, or RWA, and people with matching interests stand out on the map. Use those interests to start a conversation, grab a coffee, or explore a potential partnership. You can sign in with your wallet, and only your approximate area is shared. After meeting in person, you can both confirm the meetup and record it onchain. During KBW, add your interests and see who’s nearby. Your next conversation could lead to a new collaborator or business partner. Currently running on Injective Testnet. Give it a try—I’d love to hear what you think. @kbwofficial @injective @NinjaLabsKR

남들은 Astra로 게임만들때 Claude로 게임을 만들어봤습니다. 그동안 "게임 만들었다"는 글이나 영상은 많이 봤는데, 정작 링크 눌러서 바로 해볼 수 있게 제대로 공개된 게임은 별로 못 본 것 같습니다. 그래서 취미로 만든 게임을 공개해 봅니다. 이 게임은 브라우저에서 바로 돌아가는 1인칭 던전 탈출 게임입니다. 설치 없이 링크만 열면 됩니다. 목적은 단순합니다. 어두운 던전에서 열쇠를 찾고, 상자에서 금을 챙기고, 파란 포탈로 살아서 나오는 것. 탈출하면 체력과 랜턴 기름, 탄약을 들고 다음 층으로 내려가고, 죽으면 이번 판에서 주운 것과 그동안 모아둔 금까지 전부 잃고 1층부터 다시 시작합니다. 그래서 매 층마다 "더 탐색을 해볼까, 그냥 다음 스테이지로 넘어갈까"를 계속 고르게 됩니다. 랜턴의 사용시간은 일종의 타이머 역할을 하기도 합니다. 랜턴이 꺼지면 앞이 안 보이니 무의미하게 시간을 끌수 없습니다. 무기는 검과 머스킷인데, 검은 쓸수록 무뎌지고 머스킷은 소리가 커서 멀리 있는 적까지 몰려옵니다. 회피, 돌진 공격, 가드, 패링이 있고 바닥이나 상자에 함정도 깔려 있습니다. 층 사이에는 상점이 있어서 모은 금으로 체력 회복이나 무기 수리를 할 수 있고, 포션이나 랜턴, 와드 같은 아이템을 살 수 있습니다. 전체는 12스테이지입니다. 내려갈수록 던전이 넓어지고 적도 많아집니다. 대부분 좀비만 나오던 초반과 달리 뒤로 갈수록 훨씬 강한 적들이 섞여 나옵니다. 12층을 살아서 빠져나오면 엔딩입니다. 솔직히 만든 저도 아직 엔딩을 못 봤습니다. 혹시 보게 되시면 댓글 남겨주세요. 최대 4명까지 같이 할 수도 있으니 친구들과 즐겨보시기 바랍니다. 게임 링크와 Github 링크는 댓글로 남겨두겠습니다.

For a while, agent payments drew a great deal of attention. As standards like x402 and ERC-8004 appeared, it was often said that a world in which agents find and pay for services on a person's behalf was just around the corner. Yet when you actually looked closely, most of what existed was at the demo stage, and many observers judged that the transaction volumes being announced were closer to wash trading than to real activity. So what does it look like now that the attention has moved on? I was curious, so I built a small screen that reads on-chain data directly and left it open for several days to watch. What I saw was a steady stream of wallets paying a few cents to some service through a facilitator, with the transaction settling on Base or Polygon a few seconds later. The amounts are small and the counts are not large, but it was happening more consistently than I had expected. Attempts like x402 are ultimately about filling the place where a person used to be, and once agents start doing work with the same authority as humans, payment stops being an option and becomes a precondition. That is why I pay attention to these small numbers. Today's payment systems are all built on the assumption that there is a person in the middle. Creating an account, registering a card, and reviewing an invoice are all things a human does. But when an agent starts calling external services thousands of times a day for search, data lookups, or code execution, a person cannot step in to pay each time, and what becomes necessary is a way to pay small amounts per call without an account. The few-cent payments on my screen are what that method looks like when it actually works. This is why I believe we should be looking into and preparing for the agent payment market now, before it arrives in earnest. Which standards take hold, which facilitators handle settlement, and which chains activity gathers on are being decided now, while volumes are still small. Human payments grow one user at a time, but agent payments grow all at once when a single line of code changes. Starting to build the surrounding infrastructure at that point, such as key management, spending limits, and audit trails, would already be too late, and this quiet period is precisely the time to understand the structure and get ready. The work I am doing is aligned with this as well. For an agent to make payments without human intervention, what is needed first is not the payment protocol itself but the things that sit before and after it: keeping the agent's keys safe, defining through policy how far it is allowed to spend, and leaving a record of what it paid for. I see what has been built through node operations and custody infrastructure leading naturally in this direction, and I am preparing the infrastructure an agent needs in order to become a trustworthy paying party.

I would like to introduce an Ethereum scanner that I recently developed. This scanner connects directly to the RPC endpoint of Ethereum or Ethereum-compatible chains. As a result, it can be used immediately without any additional setup, as long as you know the RPC endpoint. This is one of its key advantages. Rather than targeting general end users, this scanner is primarily designed for developers. It is particularly useful for local network testing or for demonstrating Ethereum-compatible chains. Originally, I built this scanner as a testing tool for the mainnet I am currently developing. However, I realized that there are likely other developers who need a scanner with similar functionality for the same purpose. With that in mind, I decided to make the code public and provide a live, usable deployment as well. Live demo: code0xff.github.io/eth-ui/ Source code: github.com/code0xff/eth-ui When you first access the application, it automatically starts syncing Ethereum blocks and the corresponding transaction lists. If you want to connect to a different Ethereum-compatible network, you can stop the current sync, add a new RPC endpoint, select it, and then restart syncing. You can view detailed information using block numbers, transaction hashes, or addresses. When you access an account via its address, the interface allows you to select an ABI and perform contract calls or send transactions for that account. Since my background is mainly in core and protocol development, I am not particularly experienced in front-end development. Therefore, there may be bugs or areas that could be improved. The code is fully open-source, so if you find any issues or see opportunities for improvement, please feel free to submit a pull request. I will review it and merge it if appropriate. Thank you. @ethereum

That's really awesome.

Polkadot has been focusing on enabling the execution of Solidity-based smart contracts through a RISC-V-based PVM using a module called Revive. This approach compiles Solidity smart contract code into RISC-V-based PVM bytecode by leveraging the solc compiler together with Revive’s compiler. The goal is to provide the same developer experience as on Ethereum, thereby attracting Ethereum’s rich developer pool and dApp ecosystem, while also allowing developers to utilize the unique capabilities of the PVM. From an Ethereum developer’s perspective, if they can deploy services on Polkadot using the same codebase and also enjoy Polkadot’s unique advantages, they can either migrate to Polkadot or run services simultaneously on both chains. There are several benefits when providing services on Polkadot in particular. 1⃣ Polkadot Hub allows transaction fees to be paid not only with its native token $DOT but also with stablecoins like $USDT and tokens like $ETH. This reduces dependency on the native token and attracts a wider range of users. 2⃣ For interoperability, XCM is offered as a precompile. Simply put, this means that bridges are provided as a native feature. This contrasts with Ethereum, which relies on external services to connect with other chains. Recently, however, Polkadot announced plans to go beyond Ethereum compatibility via PVM and integrate REVM, a native EVM executor. This move aims to provide a fully identical Ethereum user experience. Since resolc (used by Revive) only supports Solidity 0.8+ and cannot run contracts written in versions below 0.8, REVM integration helps overcome this limitation. While the Frontier module was previously used in the Polkadot ecosystem for Ethereum compatibility, REVM offers better compatibility with Revive. Moreover, REVM has been widely adopted and actively developed within the Ethereum ecosystem, which contributed to its selection. Accordingly, REVM will be added to the Revive project, enabling Polkadot Hub to offer full EVM compatibility beyond just PVM-based Ethereum compatibility. The @paritytech team is currently focused on developing this feature, aiming to deploy it on Kusama—the Polkadot Canary network—by the end of October, and on Polkadot itself by mid-December. Given that Revive’s original goal was to attract dApp service providers through Ethereum compatibility, this direction seems to be an appropriate solution that reflects the ecosystem’s feedback. ✅ Developers who want to use PVM can continue to deploy contracts written in Solidity 0.8+ and offer high-performance, low-cost services. ✅ Meanwhile, developers and services that need to reuse legacy code or require full EVM compatibility can achieve their goals through REVM. This multi-VM approach will provide more options from the perspective of attracting builders and expanding the @Polkadot dApp ecosystem.

Polkadot has recently introduced additional incentives for liquidity providers to strengthen its DeFi ecosystem. The program includes not only $BTC, $ETH, $SOL and stablecoins but also a wide range of tokens from the Polkadot, Ethereum, and Solana ecosystems. Among these, I chose to provide liquidity using $SOL and receive rewards. Currently, the staking yield on the Solana network is around 7.7%. In contrast, supplying $SOL liquidity on Hydration, a DeFi platform on Polkadot, offers an APR of approximately 37.67%. Rewards are distributed in $GDOT, a liquid token backed by $DOT that can be used across various DeFi applications. To begin, I transferred my $SOL from Solana to Polkadot. I accessed Hydration, clicked the “Deposit” button in the top-right corner, selected “Another chain,” and connected my Solana wallet. I used Phantom, one of the most popular Solana wallets. After selecting Solana as the source chain and entering the amount to transfer, I input my Polkadot address as the destination and checked the “Not sending to CEX” option before proceeding. The fee was approximately 0.00278 SOL (about $0.50), which was very affordable. The transfer was routed through Wormhole to the Moonbeam network and then delivered to Hydration. Once the transfer was complete, I connected my Polkadot wallet and navigated to the “Liquidity” menu on Hydration. In the “Omnipool & Stablepools” section, I searched for “SOL” to locate the relevant liquidity pool. The current APR was shown as 37.67%, which has decreased from the initial 69% as more liquidity has been added. I clicked “Join Farms,” entered the amount of $SOL to deposit, and selected “Add Liquidity & Join Farms” to complete the process. With that, my liquidity provision was finalized, and now it’s time to receive rewards. Previously, I had only used @hydration_net for simple token swaps, but the announcement of the incentive program encouraged me to participate in a liquidity pool for the first time. What impressed me the most was Polkadot’s powerful interoperability. The transfer of $SOL from Solana through Moonbeam to Hydration took less than a minute in practice and was incredibly smooth. The fees were low and incurred only on the Solana side, with virtually no fees within Polkadot. The liquidity provisioning process was also intuitive and user-friendly, making it easy even for first-time participants. Through this experience, I was able to witness firsthand how advanced and user-centric the @Polkadot ecosystem truly is. I believe this kind of seamless and accessible environment will continue to play a key role in the growth of Polkadot-based DeFi.

The competition on the @Polkadot leaderboard has been intense. Earlier this month, I managed to climb up to 21st place, but I’ve since dropped to 54th. While I’d love to make it back into the top 50 by the end of the month, I’m starting to think it may not be realistic. Of course, I’m still actively writing and doing my best to engage with others, but maintaining my position is proving to be increasingly difficult. While it’s disappointing to see my rank fall, there’s some comfort in knowing that it’s because more influential voices on Twitter are taking an interest in Polkadot and creating great content. I’ve decided to see it as a positive — if my rank is dropping, it means more people are out there spreading the word about something I care deeply about. That said, just to be clear — this doesn’t mean I’m stepping back from the community. I’ll definitely continue contributing. I’ve just decided not to obsess over the leaderboard anymore. Honestly, over the past few days, I’ve become too fixated on it, and I ended up writing posts I wouldn’t normally write. If you’ve been following my work, you’ll know that I usually write about blockchain as a whole, and when I do focus on Polkadot, I try to approach it from fresh, meaningful angles — like the piece I wrote yesterday on how the Polkadot App could evolve into a financial infrastructure. But my recent obsession with rankings led me to create repetitive, less impactful content. That made me realize it’s time to let go of that mindset and return to writing in a way that feels true to me. Besides, contributing to Polkadot isn’t just about writing. There are other meaningful efforts I’ve started — like translating the Staking Dashboard into Korean (which I still need to finish!) and helping build a Korean community focused on Polkadot’s technology and ecosystem. My contributions go beyond leaderboard rankings, and I want to continue supporting the ecosystem in ways that reflect who I am. So from now on, I’ll focus on creating meaningful content and engaging with the community in my own way. I’m committed to contributing to the Polkadot ecosystem — and I hope we can all keep moving forward together.

As I looked at the @Polkadot App, I started to think — maybe users could use it simply as a stablecoin app, even without knowing much about Polkadot itself. If it truly works that smoothly, users might interact with the Polkadot App just for stablecoin transactions, not necessarily to engage with Web3 features. This is possible because ✅️ the Polkadot Hub offers low fees for stablecoin usage, ✅️ allows fees to be paid in stablecoins, ✅️ and provides fast transaction speeds with high throughput. As someone who believes this kind of user experience is the key to mass adoption of Web3, I’m genuinely excited about the changes the Polkadot App could bring.