Roto-Rooter Plumbing &amp; Water Cleanup (formerly called Roto-Rooter Plumbing &amp; Drain Service) is a Cincinnati, Ohio based plumbing company. The company, founded in 1935, originally specialized in clearing tree roots and other obstructions from sewer lines.

Roto-Rooter - Wikipedia

Roto-Rooter charges between $160 and $575 for basic issues ... the plumber you plan to hire offers that service. For example, many plumbing companies service water pipes, drain and sewer lines, HVAC and gas lines, while some only perform one or two of ...

Best Plumbing Companies Of 2023

It owns subsidiaries like VITAS Healthcare Corporation and Roto-Rooter, providing end-of-life hospice care and plumbing and drain cleaning services, respectively. 2. What were the key highlights of Chemed Corporation’s third-quarter 2023 results?

New Article: Chemed Corporation Reports Strong Growth in the Third Quarter of 2023

Q3 2023 Earnings Call October 26, 2023 Holley Schmidt: Good morning. Our conference call this morning will review the Financial Results for the Third Quarter of 2023 ended September 30, 2023. Before we begin,

Chemed Corporation (NYSE:CHE) Q3 2023 Earnings Call Transcript

Q3 2023 Earnings Call Transcript October 26, 2023 Holley Schmidt: Good morning. Our conference call this morning will review the Financial Results for the Third Quarter of 2023 ended September 30, 2023.

Chemed Corporation CHE reported adjusted earnings per share (EPS) of $5.32 in the third quarter of 2023, up 24.9% year over year. The figure also surpassed the Zacks Consensus Estimate by 8.1%. The company’s GAAP EPS was $4.

Chemed (CHE) Q3 Earnings and Revenues Surpass, Margins Rise

Our conference call this morning will review the financial results for the third quarter of 2023 ended September 30, 2023. Before we begin, let me remind you that the safe harbor provisions of the Private Securities Litigation Reform Act of 1995 apply to this conference call.

Q3 2023 Chemed Corp Earnings Call

Water could be seeping through a basement floor for a number of reasons, but no matter the cause, this is not a problem to ignore.

Solved! Why Is Water Seeping Through My Basement Floor?

Tucson, Arizona - J-Six Tucson Plumbing & Drain Cleaning, a leading provider of plumbing services, is thrilled to announce the opening of their new office location in Tucson, Arizona. This strategic expansion represents J-Six Tucson Plumbing's commitment to better serve the plumbing needs of residents and businesses in the Tucson,

J-Six Tucson Plumbing & Drain Cleaning Opens New Office Location in Tucson, Arizona

Chemed Corporation (Chemed) (NYSE: CHE), which operates VITAS Healthcare Corporation (VITAS), one of the nation’s largest providers of end-of-life care, and Roto-Rooter, the nation’s largest commercial and residential plumbing and drain cleaning services provider,

Chemed Reports Third-Quarter 2023 Results – Increases Full Year Guidance

Roto-Rooter Plumbing and Drain Service

rooter

GRAND CAYMAN, Cayman Islands, March 11th, 2024/Chainwire/-- The Suilend lending protocol is Solend’s first venture outside of the Solana ecosystem, underscoring confidence in Sui's technology. Suilend, Solend’s first expansion outside the Solana ecosystem, officially launched today on the Sui Network. Solend, which boasts over $200 million in total value locked (TVL) across 170,000+ users with support for 70+ assets, now brings its unparalleled DeFi expertise and experience building industry-leading lending protocols to the Sui ecosystem in a move that adds to the quickly expanding depth of the Sui ecosystem. Discussing the launch, Rooter, the pseudonymous Founder of Solend, said, "Developing on Ethereum and Solana felt like building a cathedral with chisels and hammers. That's not to say you can't build great things — cathedrals are some of the most beautiful human achievements. But we want to build rocket ships, and for that, you need advanced tools like laser cutters and welders. That's what Sui and Move offer with better developer tools." The announcement follows hot on the heels of Bluefin, a burgeoning DEX with daily volumes exceeding $100 million, committing exclusively to Sui over Arbitrum for its V2 development and unveiling its roadmap into 2024. Security is a distinct focus for participants in the DeFi space, and with the launch of Solend on Sui, the protocol is leveraging a network in Sui that has industry-leading security. By launching on Sui, Solend capitalizes on the inherent security features integrated into the Move language, which provides built-in protections for its smart contracts. Additionally, partnerships with leading blockchain security firms, Zellic and Ottersec, entail rigorous audits of projects like Suilend, ensuring adherence to the highest security standards. Suilend will also benefit from Sui’s parallel processing for most transactions. Sui boasts the lowest levels of latency in the industry and facilitates horizontal scaling, achieving a peak throughput of up to 297,000 transactions per second and a time-to-finality of approximately 480 milliseconds. "We are delighted to welcome a protocol with the background of performance and success of Suilend to the Sui ecosystem," said Greg Siourounis, Managing Director of the Sui Foundation. "Sui's blistering transaction speeds, infinite scalability and pervasive efficiency are tailor-made for DeFi projects like Suilend, and we look forward to watching their continued growth and success on Sui." This strategic move comes as Sui recently surpassed the $500 million Total Value Locked (TVL) milestone, firmly establishing itself within the top 10 DeFi ecosystems globally. Over the past month alone, a staggering $310 million in assets has migrated from Ethereum to Sui via Wormhole, eclipsing all other blockchain transfers combined, signaling the growing trust in the ecosystem’s DeFi capabilities. Contact Sui Foundation media@sui.io This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here.

Team Behind Top Lending Protocol Launches Suilend On Sui

টপ লেন্ডিং প্রোটোকলের পিছনের টিম সুইলেন্ড চালু করেছে

Das Team hinter dem Top-Lending-Protokoll führt Suilend auf Sui ein

El equipo detrás del principal protocolo de préstamos lanza Suilend On Sui

L'équipe derrière le meilleur protocole de prêt lance Suilend sur Sui

टॉप लेंडिंग प्रोटोकॉल के पीछे की टीम ने सुई पर सुइलेंड लॉन्च किया

トップレンディングプロトコルの背後にいるチームが Suilend On Sui を開始

Top Lending Protocol 팀, Suilend On Sui 출시

Equipe por trás do principal protocolo de empréstimo lança Suilend On Sui

Команда разработчиков протокола кредитования запускает Suilend On Sui

En İyi Borç Verme Protokolünün Arkasındaki Ekip Sui'de Suilend'i Başlattı

Nhóm đứng sau giao thức cho vay hàng đầu ra mắt Suilend On Sui

顶级借贷协议背后的团队在 Sui 推出 Suilend

The month of July has been nothing short of spectacular for the Indian eSports community, as the industry continues to surge forward with impressive growth and exciting developments. While mobile gaming has dominated the country’s esports landscape, PC titles are making significant strides and earning accolades as well. A slew of upcoming events promises to keep enthusiasts on the edge of their seats. PC Games Rule Too The in India has witnessed exponential growth in the past decade, enabling it to emerge as a force to be reckoned with on the global stage. While the country’s eSports landscape is mobile-dominated, PC titles are bringing in laurels too. eSports industry Amidst the traditional eSports titles that have been the founding pillars of the video-gaming industry is Street Fighter, which was earlier played in arcades but has since made its way to consoles and PCs. Mayank Prajapati and Ayan Biswas will be representing India in at the upcoming . Street Fighter V: Champion Edition Asian Games 2022 in Hangzhou Another PC title doing India proud is League of Legends. Despite the game having no official server in India, the determination and passion of Akshaj Shenoy, Aditya Selvaraj, Aakash Shandilya, Mihir Ranjan, Sanindhya Malik, and Samarth Trivedi saw them utilize their skills to impressively qualify for the 19th Asian Games Hangzhou. The star-studded unit battled against the odds to secure their berth at the prestigious tournament. The team also produced dazzling displays in the Central and South Asia seeding event to not only ensure favorable seeding at the tournament but also emerge as a powerhouse amongst the 19 teams that will be competing in the title. Event Sketch Other upcoming events in include and BGMS Season 2 with Rooter as the digital streaming partner. The event will kick off on August 4, 2023, with a prize pool of INR 2.1 crore and will feature 24 esports teams. NODWIN Gaming has also announced its partnership with Indian two-wheeler manufacturing giant as the tournament’s mobility partner. esports Nodwin Gaming Star Sports’ TVS Motor Company In addition, NODWIN tied up with video game publisher , celebrated the successful culmination of India’s first publisher-supported esports league in the VALORANT Challengers South Asia in 2023. The 60-day VALORANT esports showcase from the South Asian zone offered a prize pool of US$140,000. It started with Split 1 on March 18 and ended with the best-of-5 Split 2 grand finals on June 10. Riot Games eSports Tie Ups In July, tied up with further venturing into the world of gaming with the launch of its BGMI E-Sports team, named ‘OneBlade’. Philips India BGMI E-Sports tied up with esports performance and wellness company , a Vancouver-based performance-focused brand that provides esports athletes with the tools to train and perform for competitive gaming challenges. Global Esports will utilize the services to bolster the out-of-game performance of the VALORANT roster. Global Esports Adamas an Asian esports organization, tied up with | AORUS, a manufacturer of motherboards and graphics cards, for the Skyesports Masters, India’s first franchised esports league with a Rs. 2,00,00,000 prize pool. Revenant Esports, Gigabyte New Game Launch , a Taiwanese gaming corporation, revealed plans to expand its footprint in the Indian gaming market by launching Starlight Gaming, which launched a Battle Royale game, Raider SIX. According to the company, the game garnered close to 1.2 million downloads in just 7 days. Softstar Entertainment Inc. Sharing his enthusiasm, actor Sidharth Malhotra, said, “’Raider SIX’ is a fun game to play. The game captures the spirit of Indian culture while providing a unique and exhilarating gaming experience. I can clearly recall my childhood play when I would use my toy rifle and go on grand adventures. It brings back those priceless memories to be a part of this event where gaming meets real-world events. I’m having a wonderful time and feel excited to be a part of this amazing event.” Raider SIX is a Battle Royale Action mobile game that immerses players in an Indian battle landscape. Tailored exclusively for the Indian gaming community, it aims to capture the hearts of Indian gamers with a rich tapestry of characters and aesthetic scenery. The game includes Indian-style characters with renamable names. This article was originally published by Navanwita Bora Sachdev The Tech Panda.

Exploring Indian eSports: Triumphs, Partnerships, and Game Launches

At the Earth's Core by Edgar Rice Burroughs, is part of the HackerNoon Books Series. You can jump to any chapter in this book here . THE SLY ONE THE SLY ONE THE SAGOTHS WERE GAINING ON US RAPIDLY, FOR once they had sighted us they had greatly increased their speed. On and on we stumbled up the narrow canyon that Ghak had chosen to approach the heights of Sari. On either side rose precipitous cliffs of gorgeous, parti-colored rock, while beneath our feet a thick mountain grass formed a soft and noiseless carpet. Since we had entered the canyon we had had no glimpse of our pursuers, and I was commencing to hope that they had lost our trail and that we would reach the now rapidly nearing cliffs in time to scale them before we should be overtaken. Ahead we neither saw nor heard any sign which might betoken the success of Hooja's mission. By now he should have reached the outposts of the Sarians, and we should at least hear the savage cries of the tribesmen as they swarmed to arms in answer to their king's appeal for succor. In another moment the frowning cliffs ahead should be black with primeval warriors. But nothing of the kind happened—as a matter of fact the Sly One had betrayed us. At the moment that we expected to see Sarian spearmen charging to our relief at Hooja's back, the craven traitor was sneaking around the outskirts of the nearest Sarian village, that he might come up from the other side when it was too late to save us, claiming that he had become lost among the mountains. Hooja still harbored ill will against me because of the blow I had struck in Dian's protection, and his malevolent spirit was equal to sacrificing us all that he might be revenged upon me. As we drew nearer the barrier cliffs and no sign of rescuing Sarians appeared Ghak became both angry and alarmed, and presently as the sound of rapidly approaching pursuit fell upon our ears, he called to me over his shoulder that we were lost. A backward glance gave me a glimpse of the first of the Sagoths at the far end of a considerable stretch of canyon through which we had just passed, and then a sudden turning shut the ugly creature from my view; but the loud howl of triumphant rage which rose behind us was evidence that the gorilla-man had sighted us. Again the canyon veered sharply to the left, but to the right another branch ran on at a lesser deviation from the general direction, so that appeared more like the main canyon than the lefthand branch. The Sagoths were now not over two hundred and fifty yards behind us, and I saw that it was hopeless for us to expect to escape other than by a ruse. There was a bare chance of saving Ghak and Perry, and as I reached the branching of the canyon I took the chance. Pausing there I waited until the foremost Sagoth hove into sight. Ghak and Perry had disappeared around a bend in the left-hand canyon, and as the Sagoth's savage yell announced that he had seen me I turned and fled up the right-hand branch. My ruse was successful, and the entire party of man-hunters raced headlong after me up one canyon while Ghak bore Perry to safety up the other. Running has never been my particular athletic forte, and now when my very life depended upon fleetness of foot I cannot say that I ran any better than on the occasions when my pitiful base running had called down upon my head the rooter's raucous and reproachful cries of "Ice Wagon," and "Call a cab." The Sagoths were gaining on me rapidly. There was one in particular, fleeter than his fellows, who was perilously close. The canyon had become a rocky slit, rising roughly at a steep angle toward what seemed a pass between two abutting peaks. What lay beyond I could not even guess—possibly a sheer drop of hundreds of feet into the corresponding valley upon the other side. Could it be that I had plunged into a cul-de-sac? Realizing that I could not hope to outdistance the Sagoths to the top of the canyon I had determined to risk all in an attempt to check them temporarily, and to this end had unslung my rudely made bow and plucked an arrow from the skin quiver which hung behind my shoulder. As I fitted the shaft with my right hand I stopped and wheeled toward the gorilla-man. In the world of my birth I never had drawn a shaft, but since our escape from Phutra I had kept the party supplied with small game by means of my arrows, and so, through necessity, had developed a fair degree of accuracy. During our flight from Phutra I had restrung my bow with a piece of heavy gut taken from a huge tiger which Ghak and I had worried and finally dispatched with arrows, spear, and sword. The hard wood of the bow was extremely tough and this, with the strength and elasticity of my new string, gave me unwonted confidence in my weapon. Never had I greater need of steady nerves than then—never were my nerves and muscles under better control. I sighted as carefully and deliberately as though at a straw target. The Sagoth had never before seen a bow and arrow, but of a sudden it must have swept over his dull intellect that the thing I held toward him was some sort of engine of destruction, for he too came to a halt, simultaneously swinging his hatchet for a throw. It is one of the many methods in which they employ this weapon, and the accuracy of aim which they achieve, even under the most unfavorable circumstances, is little short of miraculous. My shaft was drawn back its full length—my eye had centered its sharp point upon the left breast of my adversary; and then he launched his hatchet and I released my arrow. At the instant that our missiles flew I leaped to one side, but the Sagoth sprang forward to follow up his attack with a spear thrust. I felt the swish of the hatchet as it grazed my head, and at the same instant my shaft pierced the Sagoth's savage heart, and with a single groan he lunged almost at my feet—stone dead. Close behind him were two more—fifty yards perhaps—but the distance gave me time to snatch up the dead guardsman's shield, for the close call his hatchet had just given me had borne in upon me the urgent need I had for one. Those which I had purloined at Phutra we had not been able to bring along because their size precluded our concealing them within the skins of the Mahars which had brought us safely from the city. With the shield slipped well up on my left arm I let fly with another arrow, which brought down a second Sagoth, and then as his fellow's hatchet sped toward me I caught it upon the shield, and fitted another shaft for him; but he did not wait to receive it. Instead, he turned and retreated toward the main body of gorilla-men. Evidently he had seen enough of me for the moment. Once more I took up my flight, nor were the Sagoths apparently overanxious to press their pursuit so closely as before. Unmolested I reached the top of the canyon where I found a sheer drop of two or three hundred feet to the bottom of a rocky chasm; but on the left a narrow ledge rounded the shoulder of the overhanging cliff. Along this I advanced, and at a sudden turning, a few yards beyond the canyon's end, the path widened, and at my left I saw the opening to a large cave. Before, the ledge continued until it passed from sight about another projecting buttress of the mountain. Here, I felt, I could defy an army, for but a single foeman could advance upon me at a time, nor could he know that I was awaiting him until he came full upon me around the corner of the turn. About me lay scattered stones crumbled from the cliff above. They were of various sizes and shapes, but enough were of handy dimensions for use as ammunition in lieu of my precious arrows. Gathering a number of stones into a little pile beside the mouth of the cave I waited the advance of the Sagoths. As I stood there, tense and silent, listening for the first faint sound that should announce the approach of my enemies, a slight noise from within the cave's black depths attracted my attention. It might have been produced by the moving of the great body of some huge beast rising from the rock floor of its lair. At almost the same instant I thought that I caught the scraping of hide sandals upon the ledge beyond the turn. For the next few seconds my attention was considerably divided. And then from the inky blackness at my right I saw two flaming eyes glaring into mine. They were on a level that was over two feet above my head. It is true that the beast who owned them might be standing upon a ledge within the cave, or that it might be rearing up upon its hind legs; but I had seen enough of the monsters of Pellucidar to know that I might be facing some new and frightful Titan whose dimensions and ferocity eclipsed those of any I had seen before. Whatever it was, it was coming slowly toward the entrance of the cave, and now, deep and forbidding, it uttered a low and ominous growl. I waited no longer to dispute possession of the ledge with the thing which owned that voice. The noise had not been loud—I doubt if the Sagoths heard it at all—but the suggestion of latent possibilities behind it was such that I knew it would only emanate from a gigantic and ferocious beast. As I backed along the ledge I soon was past the mouth of the cave, where I no longer could see those fearful flaming eyes, but an instant later I caught sight of the fiendish face of a Sagoth as it warily advanced beyond the cliff's turn on the far side of the cave's mouth. As the fellow saw me he leaped along the ledge in pursuit, and after him came as many of his companions as could crowd upon each other's heels. At the same time the beast emerged from the cave, so that he and the Sagoths came face to face upon that narrow ledge. The thing was an enormous cave bear, rearing its colossal bulk fully eight feet at the shoulder, while from the tip of its nose to the end of its stubby tail it was fully twelve feet in length. As it sighted the Sagoths it emitted a most frightful roar, and with open mouth charged full upon them. With a cry of terror the foremost gorilla-man turned to escape, but behind him he ran full upon his on-rushing companions. The horror of the following seconds is indescribable. The Sagoth nearest the cave bear, finding his escape blocked, turned and leaped deliberately to an awful death upon the jagged rocks three hundred feet below. Then those giant jaws reached out and gathered in the next—there was a sickening sound of crushing bones, and the mangled corpse was dropped over the cliff's edge. Nor did the mighty beast even pause in his steady advance along the ledge. Shrieking Sagoths were now leaping madly over the precipice to escape him, and the last I saw he rounded the turn still pursuing the demoralized remnant of the man hunters. For a long time I could hear the horrid roaring of the brute intermingled with the screams and shrieks of his victims, until finally the awful sounds dwindled and disappeared in the distance. Later I learned from Ghak, who had finally come to his tribesmen and returned with a party to rescue me, that the ryth, as it is called, pursued the Sagoths until it had exterminated the entire band. Ghak was, of course, positive that I had fallen prey to the terrible creature, which, within Pellucidar, is truly the king of beasts. Not caring to venture back into the canyon, where I might fall prey either to the cave bear or the Sagoths I continued on along the ledge, believing that by following around the mountain I could reach the land of Sari from another direction. But I evidently became confused by the twisting and turning of the canyons and gullies, for I did not come to the land of Sari then, nor for a long time thereafter. About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. Edgar Rice Burroughs (1994). At the Earth's Core. Urbana, Illinois: Project Gutenberg. Retrieved October 2022 https://www.gutenberg.org/cache/epub/123/pg123-images.html This eBook is for the use of anyone anywhere at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at www.gutenberg.org , located at https://www.gutenberg.org/policy/license.html.

THE SLY ONE

Imagine you wake up one morning to find that your DeFi lending protocol is on the verge of a liquidation. “What’s the big deal? Liquidations happen all the time,” you say. No big deal except it could trigger a chain of events that would potentially collapse a whole blockchain and render a cryptocurrency useless. “How did this happen again?” Long story short,  you loaned 95% of your crypto deposits to a single whale. “Is this for real?” Yep. That’s what happened to Solend, Solana’s largest lending DeFi protocol when Sol’s value plummeted and came dangerously close to a hefty margin call. If Sol had plummeted to $22.30, it would have automatically liquidated 20% of a single user’s loan— $108 million USDC and USDT borrowed against 5.7 million ($170 million) in SOL collateral and caused a huge risk to the network. Yes, it’s not uncommon for DeFi apps to deposit a large volume of tokens in collateral when users wish to borrow against other tokens. Other popular DeFi lending platforms like Compound, AAVE, and Maker had done this before and handled large-scale on-chain liquidations without breaking a sweat. But the same can’t be said for Solana, as it has already crashed in the past and straining the DEX with a $21 million liquidation will not bode well for its users. Additionally, the incident will incentivize other liquidators on the chain to spam the network with liquidations and earn lucrative profits for their efforts, further damaging the network. That’s not all. Since SOL’s liquidity pools can’t handle such a huge transaction, it would fail and cause bad debt. It would also cause users to pull out funds and cause Sol prices to drop to historic lows. In short, one transaction would snowball into a huge crisis for Solana. So, what did Solend do to avert the crisis, and what can we learn from the fiasco? We’ll answer these burning questions while breaking down the Solend fiasco in this article. Contingency Measures Solend’s pseudonymous co-founder Rooter took to social media sites like Twitter and Reddit to get in touch with the whale and get them to pay more collateral. Source: Twitter But the whale refused to restructure the loan and the plan went bust. So, instead of stopping withdrawals like Celsius did, Solend canceled all borrowings. So far, so good. But they still had to get an Over-The-Counter (OTC) trade and here’s where they messed up. They took a drastic step and held a governance vote to hijack the user’s wallet and execute the trade themselves. Source: Realms Since Solend was stuck between a rock and a hard place which threatened the collapse of a whole blockchain, they chose the lesser evil. Still, one can’t deny that the move was unethical and went against the ethos of crypto. Twitter and Reddit users called it a “centralized” move that set the wrong precedent for DeFi because: Solend gave its users no more than 6 hours to vote. The lion’s share of the vote came from another whale. (So much for decentralization.) Source: Realms After the online backlash, Solend held another governance vote to overrule the previous one. By this point, Rooter’s parallel outreach efforts had borne fruit, and they’d found another way to convince the whale. Source: Realms Binance Saves The Day Binance, the world’s largest cryptocurrency exchange, managed to get in touch with the borrower whale via email after which Solend members convinced them to restructure and redistribute their loan. Over the next few days, the whale moved their loan from Solend to Mango Markets, another DeFi lender on Solana. The SOL Token price also climbed steadily and reached a stable $38.55 by that time (June 23rd), so the crisis was averted. Rooter also took to Reddit for an to underscore Solend’s future measures and answer users' questions about the crisis. AMA session Next Steps After the Solend fiasco, Solend held a third governance vote to limit the borrowing to $50 million and said that any debt above the limit would be eligible for liquidation regardless of the collateral value. Source: Realms It also reduced the liquidation factor from 20% to 1% and reduced the liquidation penalty from 5% to 2% to reduce the network's strain and liquidator spam. The proposal also stated that Solend is reaching out to market makers to improve on-chain liquidity and reduce DEX market impact to a manageable level. But how could Solend have prevented this from happening in the first place? For starters, it could’ve prevented over-collateralization. Yes, this practice is pervasive in the crypto-community owing to the anonymity and the high returns such activities bring. But the trend has now reversed, and the Total Value Locked (TVL) for all crypto assets . So, Solend could’ve avoided going down this path, given that they kept tabs on market trends and had a fair idea of their liquidity pools’ capabilities. has plummeted And when it comes to governance, there’s no doubt that Solend sucks big time. Currently, it has a stake-based voting system where 1 token constitutes 1 vote. The primary idea behind this system is that a higher stake would mean that the person would vote such that the protocol succeeds and they reap mutual benefits. In other words, the greater the stake, the better the governance decisions. But this is a naive approach as there’s no guarantee that a person holding many tokens would make the right decisions. Also, people who hold high stakes in a DAO are more likely to be too rich and too busy to participate, as shown by the graph below. Source: Maker DAO So, Solend would be better off if it adopted more efficient voting mechanisms like 1 Person, 1 Vote (1P 1V), wherein members must produce a “proof of stake” to vote, and everyone holding X amount of DAO governance tokens have the same voting power. They can also go down Oxford Blockchain Society DAO’s path and impose a ceiling wherein no member of the DAO can hold more than X% of the governance tokens. There are also other voting mechanisms like , which can be used in combination with their existing mechanism or the 1P1V method, but this may hinder members from participating in the vote as it makes the process too complex. liquid democracy and holographic voting Closing Thoughts Solend is a promising protocol, and it aims to leverage Solana’s cheap transaction fees and high throughput to make it the preferred destination for DeFi. But it’s still too early to bite off more than it can chew, so Solend must take the necessary measures to bring liquidity to its platform before lending out massive loans. Also, right now, a lot of Solend users are backing out of the platform because of the deep-rooted centralization embedded in the governance and the Solana platform itself. So, the protocol must work to better its governance to earn back the trust of the crypto community and ensure that their contributions to DeFi are taken seriously.

Solend Bloodbath: How A Single Whale Almost Brought Down The Solana Blockchain

Baño de sangre de Solend: cómo una sola ballena casi derriba la cadena de bloques de Solana

Bain de sang de Solend : comment une seule baleine a presque fait tomber la blockchain de Solana

सोलेंड ब्लडबाथ: कैसे एक सिंगल व्हेल ने सोलाना ब्लॉकचैन को लगभग गिरा दिया

Solend Bloodbath: 1 頭のクジラがどのようにして Solana ブロックチェーンを崩壊させようとしたか

Solend Bloodbath: como uma única baleia quase derrubou o Solana Blockchain

Solend Bloodbath: Cách một con cá voi duy nhất gần như hạ gục chuỗi khối Solana

Solend Bloodbath：一只鲸鱼是如何几乎摧毁 Solana 区块链的

A brief history of my journey with vue-router Virtually every developer using Vue.js is currently using or has only ever used Vue-router. Many of those developers, myself included, are mostly happy with it. The biggest complaint I hear is the lack of strongly typed routes, which is usually solved with a bit of Typescript wrapping your routes. // router/routes.ts
import { RouteLocationRaw, RouteRecordRaw } from 'vue-router'

type RouteFunction = (...args: any[]) => RouteLocationRaw

export const routes = {
 home: () => ({ name: 'home' }) as const,
 club: (clubId: string) => ({ name: 'clubs.view', params: { clubId } }) as const,
 profile: (userId?: string) => ({ name: 'profile.view', query: { userId } }) as const,
} satisfies Record<string, RouteFunction> Then routes becomes your source of truth, so navigation should always use a route from routes to send proper names to vue-router. <router-link :to="routes.club('club-123')">go to club</router-link> The syntax of defining routes is a bit cumbersome but honestly works fairly well. However, because I’m a serial starter-of-new-projects and love a challenge, I teamed up with Pleek91 to see if we could build our own. Introducing Kitbag Router https://router.kitbag.dev We made the decision to start the project from scratch; solving problems from first principles rather than taking the path of so many others and trying to build on top of the relatively old vue-router project. This means Kitbag Router is NOT a drop-in replacement for projects using vue-router. Therefore, this freedom also means we can have a relentless pursuit of the best possible developer experience, not weighed down by the need to have feature parity with Vue-router. Let’s take a look at some of Kitbag’s features First and foremost, it’s type safe! Kitbag Router uses a createRoutes utility that returns routes with the name, path, and query, all preserved in the Route type. This means the routes you provide to createRouter will maintain type safety when accessing the current route or performing navigation. Type safety in routing means auto-complete when assigning to on <router-link>, the easy discovery of available routes when defining a beforeRouteEnter hook, and ensuring that Typescript will error if the expected params for a route change without updating the router.push() call. Params are way more powerful Not only does Kitbag Router know what params are expected for a given route, it can also support param types beyond String. Kitbag Router ships with built-in support for params of typeString, Number, Boolean, Date, RegExp, JSON, as well as any custom param type you define. Not only is this type useful when navigating, but it also means a route that expects a number for an “id” param won’t be considered a match if the value provided in the URL doesn’t satisfy the number constraint. Furthermore, your Vue component that gets rendered for the route doesn’t have to worry about whether the param will be present or not or having to convert it from string to the type we know it’s supposed to be. Support for the query Params aren’t relegated to only the path. Kitbag Router allows you to configure your expected params in the query the same way you’re used to defining params in other parts of the URL. Handling rejections Inevitably when defining your routes, you’ll want to add a “catch-all” or “not found” route. While Kitbag Router fully supports defining plain ol’ Regex in your path/query, it also ships with even better support for handling NotFound. We call this a “rejection”, which is customizable and can be extended to any custom rejection you need, like perhaps NotAuthorized. When a rejection is triggered, usually from within one of your hooks, the Kitbag Router will automatically render the rejection component you assigned for the given rejection type. And more… These are the key features we think really make Kitbag Router compelling but there is so much more. Kitbag router is built for Vue3 and supports async components, route hooks, editable params from useRoute, components for RouterLink and RouterView, and more. Is it ready? Kitbag Router is still super green and currently maintained by a team of 2. It has not yet had a stable release (on 0.2.0 as of the time I’m writing this), so things are still likely to change. That being said, I hope you’ll give it a try, maybe give it a star. We’re excited to hear from the community on what features we should focus on next. Happy engineering! A brief history of my journey with vue-router Virtually every developer using Vue.js is currently using or has only ever used Vue-router. Many of those developers, myself included, are mostly happy with it. The biggest complaint I hear is the lack of strongly typed routes, which is usually solved with a bit of Typescript wrapping your routes. Vue.js // router/routes.ts
import { RouteLocationRaw, RouteRecordRaw } from 'vue-router'

type RouteFunction = (...args: any[]) => RouteLocationRaw

export const routes = {
 home: () => ({ name: 'home' }) as const,
 club: (clubId: string) => ({ name: 'clubs.view', params: { clubId } }) as const,
 profile: (userId?: string) => ({ name: 'profile.view', query: { userId } }) as const,
} satisfies Record<string, RouteFunction> // router/routes.ts
import { RouteLocationRaw, RouteRecordRaw } from 'vue-router'

type RouteFunction = (...args: any[]) => RouteLocationRaw

export const routes = {
 home: () => ({ name: 'home' }) as const,
 club: (clubId: string) => ({ name: 'clubs.view', params: { clubId } }) as const,
 profile: (userId?: string) => ({ name: 'profile.view', query: { userId } }) as const,
} satisfies Record<string, RouteFunction> Then routes becomes your source of truth, so navigation should always use a route from routes to send proper names to vue-router. routes routes <router-link :to="routes.club('club-123')">go to club</router-link> <router-link :to="routes.club('club-123')">go to club</router-link> The syntax of defining routes is a bit cumbersome but honestly works fairly well. However, because I’m a serial starter-of-new-projects and love a challenge, I teamed up with Pleek91 to see if we could build our own. Pleek91 Introducing Kitbag Router https://router.kitbag.dev https://router.kitbag.dev We made the decision to start the project from scratch; solving problems from first principles rather than taking the path of so many others and trying to build on top of the relatively old vue-router project. This means Kitbag Router is NOT a drop-in replacement for projects using vue-router. Therefore, this freedom also means we can have a relentless pursuit of the best possible developer experience, not weighed down by the need to have feature parity with Vue-router. Let’s take a look at some of Kitbag’s features Let’s take a look at some of Kitbag’s features First and foremost, it’s type safe! Kitbag Router uses a createRoutes utility that returns routes with the name, path, and query, all preserved in the Route type. This means the routes you provide to createRouter will maintain type safety when accessing the current route or performing navigation. Type safety in routing means auto-complete when assigning to on <router-link> , the easy discovery of available routes when defining a beforeRouteEnter hook, and ensuring that Typescript will error if the expected params for a route change without updating the router.push() call. <router-link> beforeRouteEnter router.push() Params are way more powerful Not only does Kitbag Router know what params are expected for a given route, it can also support param types beyond String . String Kitbag Router ships with built-in support for params of typeString, Number , Boolean , Date , RegExp , JSON , as well as any custom param type you define. Number Boolean Date RegExp JSON Not only is this type useful when navigating, but it also means a route that expects a number for an “id” param won’t be considered a match if the value provided in the URL doesn’t satisfy the number constraint. Furthermore, your Vue component that gets rendered for the route doesn’t have to worry about whether the param will be present or not or having to convert it from string to the type we know it’s supposed to be. number Support for the query Params aren’t relegated to only the path. Kitbag Router allows you to configure your expected params in the query the same way you’re used to defining params in other parts of the URL. Handling rejections Inevitably when defining your routes, you’ll want to add a “catch-all” or “not found” route. While Kitbag Router fully supports defining plain ol’ Regex in your path/query, it also ships with even better support for handling NotFound . We call this a “rejection”, which is customizable and can be extended to any custom rejection you need, like perhaps NotAuthorized . When a rejection is triggered, usually from within one of your hooks, the Kitbag Router will automatically render the rejection component you assigned for the given rejection type. NotFound NotAuthorized And more… These are the key features we think really make Kitbag Router compelling but there is so much more. Kitbag router is built for Vue3 and supports async components, route hooks, editable params from useRoute, components for RouterLink and RouterView, and more. Is it ready? Kitbag Router is still super green and currently maintained by a team of 2. It has not yet had a stable release (on 0.2.0 as of the time I’m writing this), so things are still likely to change. That being said, I hope you’ll give it a try, maybe give it a star . We’re excited to hear from the community on what features we should focus on next. give it a star Happy engineering!

Say Hello to Kitbag Router: A New Era of Vue.js Routing

Router Protocol is pleased to announce that it has completed an oversubscribed strategic funding round with participation from prominent crypto angels and funds. The primary goal of the strategic round was to thoughtfully expand Router's cap table with crypto operators who deeply understand the importance of cross-chain infrastructure and can accelerate the ecosystem growth as Router evolves into a Layer 1 blockchain. Router Protocol is honored to welcome an exceptional group of accomplished founders and web3 executives as angels and advisors, including Keone Hon (Monad), Parker Jou (Caldera), Amrit Kumar (Altlayer), Aniket (Biconomy), Anurag Arjun (Avail), Amitej (Stader), Ravindra (Frontier), and several others. In a testament to the unwavering belief in its vision, Router Protocol also received overwhelming support from existing investors, including heavyweight players such as Wintermute Ventures, Woodstock, DeFi Capital, CryptoBanter, RavenDAO, and Luganodes. Other renowned advisors and angels include Zaki Manian (Sommelier/Cosmos), Ajit Tripathi (@chainyoda), Gokul Rajaram (Google/Doordash), and Surojit Chatterjee (Coinbase, Google, Flipkart, EMA). The proceeds from this funding round will be deployed strategically to fuel the development and highly anticipated launch of the Router Chain mainnet. Router Chain is set to revolutionize value transfer by abstracting away blockchain complexity and unlocking a new era of frictionless cross-chain applications and user experiences. "Router Chain embodies the evolution of our unwavering vision to build the universal interconnectivity layer between fragmented L1/L2 networks," said Ramani Ramachandran, CEO of Router Protocol. "By abstracting away blockchain complexity, we are laser-focused on delivering the most seamless and intuitive user and developer experience for multi-chain applications. This funding round propels us closer to realising this transformative vision." Router Protocol’s mantra has always been "developers first." Its mission is to empower builders to focus on bringing their groundbreaking ideas to life, rather than grappling with infrastructure complexities. Router Chain will provide a robust suite of flexible interoperability primitives, including its innovative cross-chain intent framework and developer-friendly toolkits, to make this vision a reality. "We are thrilled to witness the rapid expansion of our ecosystem, with trailblazing cross-chain projects like StakeEase, FolioX, and many more leveraging our interoperability primitives to push the boundaries of what's possible," said Shubham Singh, CTO of Router Protocol. In a major milestone, Router Protocol launched Router Nitro, a super-fast, gas-efficient, intent-based cross-chain bridge powered by an innovative reverse-verification mechanism. Nitro Bridge crossed $350M volume in the past 4 months, over 650K+ transactions, and almost 300K unique users. To further accelerate ecosystem growth, Router Protocol is thrilled to announce the upcoming launch of the Router Ecosystem Grants Program, which will provide substantial financial support and resources to promising projects building on Router Chain. Moreover, the project’s recently revamped tokenomics empowers it to aggressively focus on community engagement, ecosystem expansion, and the promotion of exciting new cross-chain primitives that will redefine the landscape of interoperability. The oversubscribed round demonstrates the demand for high-value web3 infrastructure and marks a crucial step in Router's maturation from a bridge solution to a core Web3 connecting layer. Backing from this expanded group of partners will aid in evangelizing Router's vision and unique value proposition to a global audience. Router Protocol is pleased to announce that it has completed an oversubscribed strategic funding round with participation from prominent crypto angels and funds. Router Protocol is pleased to announce that it has completed an oversubscribed strategic funding round with participation from prominent crypto angels and funds. The primary goal of the strategic round was to thoughtfully expand Router's cap table with crypto operators who deeply understand the importance of cross-chain infrastructure and can accelerate the ecosystem growth as Router evolves into a Layer 1 blockchain. Router Protocol is honored to welcome an exceptional group of accomplished founders and web3 executives as angels and advisors, including Keone Hon (Monad), Parker Jou (Caldera), Amrit Kumar (Altlayer), Aniket (Biconomy), Anurag Arjun (Avail), Amitej (Stader), Ravindra (Frontier), and several others. In a testament to the unwavering belief in its vision, Router Protocol also received overwhelming support from existing investors, including heavyweight players such as Wintermute Ventures, Woodstock, DeFi Capital, CryptoBanter, RavenDAO, and Luganodes. Other renowned advisors and angels include Zaki Manian (Sommelier/Cosmos), Ajit Tripathi (@chainyoda), Gokul Rajaram (Google/Doordash), and Surojit Chatterjee (Coinbase, Google, Flipkart, EMA). The proceeds from this funding round will be deployed strategically to fuel the development and highly anticipated launch of the Router Chain mainnet. Router Chain is set to revolutionize value transfer by abstracting away blockchain complexity and unlocking a new era of frictionless cross-chain applications and user experiences. "Router Chain embodies the evolution of our unwavering vision to build the universal interconnectivity layer between fragmented L1/L2 networks," said Ramani Ramachandran, CEO of Router Protocol. "By abstracting away blockchain complexity, we are laser-focused on delivering the most seamless and intuitive user and developer experience for multi-chain applications. This funding round propels us closer to realising this transformative vision." Router Protocol’s mantra has always been "developers first." Its mission is to empower builders to focus on bringing their groundbreaking ideas to life, rather than grappling with infrastructure complexities. Router Chain will provide a robust suite of flexible interoperability primitives, including its innovative cross-chain intent framework and developer-friendly toolkits, to make this vision a reality. "We are thrilled to witness the rapid expansion of our ecosystem, with trailblazing cross-chain projects like StakeEase, FolioX, and many more leveraging our interoperability primitives to push the boundaries of what's possible," said Shubham Singh, CTO of Router Protocol. In a major milestone, Router Protocol launched Router Nitro, a super-fast, gas-efficient, intent-based cross-chain bridge powered by an innovative reverse-verification mechanism. Nitro Bridge crossed $350M volume in the past 4 months, over 650K+ transactions, and almost 300K unique users. To further accelerate ecosystem growth, Router Protocol is thrilled to announce the upcoming launch of the Router Ecosystem Grants Program, which will provide substantial financial support and resources to promising projects building on Router Chain. Moreover, the project’s recently revamped tokenomics empowers it to aggressively focus on community engagement, ecosystem expansion, and the promotion of exciting new cross-chain primitives that will redefine the landscape of interoperability. The oversubscribed round demonstrates the demand for high-value web3 infrastructure and marks a crucial step in Router's maturation from a bridge solution to a core Web3 connecting layer. Backing from this expanded group of partners will aid in evangelizing Router's vision and unique value proposition to a global audience.

Router Protocol Completes Oversubscribed Strategic Funding Round

রাউটার প্রোটোকল ওভারসাবস্ক্রাইবড স্ট্র্যাটেজিক ফান্ডিং রাউন্ড সম্পূর্ণ করে

Router Protocol schließt überzeichnete strategische Finanzierungsrunde ab

Router Protocol completa una ronda de financiación estratégica con exceso de suscripción

Le protocole de routeur finalise un cycle de financement stratégique sursouscrit

राउटर प्रोटोकॉल ने ओवरसब्सक्राइब्ड रणनीतिक फंडिंग राउंड पूरा किया

ルータープロトコル、募集額超過の戦略的資金調達ラウンドを完了

라우터 프로토콜, 초과 구독된 전략적 자금 조달 라운드 완료

Router Protocol conclui rodada de financiamento estratégico com excesso de inscrições

Router Protocol завершает раунд стратегического финансирования переподписки

Yönlendirici Protokolü Aşırı Abone Olunan Stratejik Finansman Turunu Tamamladı

Giao thức bộ định tuyến hoàn thành vòng tài trợ chiến lược được đăng ký vượt mức

路由器协议完成超额认购的战略融资轮

Introduction For those who have never worked with Feature-Sliced Design, aka I recommend reading my article about FSD first. FSD, https://hackernoon.com/the-best-complex-frontend-architecture-what-you-need-to-know-about-feature-sliced-design?embedable=true Many developers faced a problem when starting a project using NextJS with FSD, spending time to get it right to combine NextJS and FSD to make it work together, especially using the NextJS App Router. This article describes how to make NextJS App Router work with the FSD methodology. Problem NextJS App Router expects files in the . This routing mechanism to the FSD concept since it is not possible to maintain a flat slice structure in such a routing mechanism. app folder to match URLs does not correspond Approach The approach is pretty simple. You should simply move the NextJS folder to the root folder of the project, and import the FSD pages into the NextJS folder. This saves the FSD project structure inside the folder. app app src ├── app                # NextJS app folder
├── src
│   ├── app            # FSD app folder
│   ├── entities
│   ├── features
│   ├── pages
│   ├── shared
│   ├── widgets And that's it! The problem of combining NextJS App Router and FSD is solved! See Also I highly recommend reading the official FSD documentation article about Usage with NextJS

How to Fix the NextJS App Router and FSD Problem

How to Write Your Own Typesafe React Router in 500 Lines

কিভাবে 500 লাইনে আপনার নিজের টাইপসেফ রিঅ্যাক্ট রাউটার লিখবেন

So schreiben Sie Ihren eigenen typsicheren React-Router in 500 Zeilen

Cómo escribir su propio enrutador Typesafe React en 500 líneas

Comment écrire votre propre routeur Typesafe React en 500 lignes

500 पंक्तियों में अपना खुद का टाइपसेफ रिएक्ट राउटर कैसे लिखें

独自のタイプセーフな React Router を 500 行で書く方法

500줄로 나만의 Typesafe React Router를 작성하는 방법

Como escrever seu próprio roteador Typesafe React em 500 linhas

Как написать свой собственный Typesafe React Router в 500 строк

Kendi Typesafe React Router'ınızı 500 Satırda Nasıl Yazabilirsiniz?

Cách viết Bộ định tuyến React Typesafe của riêng bạn trong 500 dòng

如何用 500 行代码编写自己的类型安全 React 路由器

VANCOUVER, BC, Canada, November 6th, 2023/Chainwire/--MaestroBots, a prominent cryptocurrency trading bot on the Telegram messenger app, has swiftly taken action to refund users who were affected by a recent smart contract exploit. In an incident that unfolded on October 24, a total of 280 ETH was targeted. In response, the Maestro team took immediate action to refund the users impacted by the Maestro Router 2 contract exploit. This commitment to user security and trust was announced on social media platform X (formerly Twitter) on October 25. MaestroBots allocated a substantial sum of 610 ETH from its own revenue to cover all user losses. At the time of writing, this sum exceeded $1 million. The statement from MaestroBots read: "Every wallet that lost tokens in the router exploit has now received the full amount they lost. Some of you ended up with even bigger bags." For nine out of the 11 exploited tokens, MaestroBots opted to buy and refund tokens, instead of sending ETH, deeming it the most equitable and comprehensive refund. MaestroBots spent 276 ETH to secure users' tokens, demonstrating their commitment to user safety. For the remaining two tokens, Joe (JOE) and Lockheed Martin Inu (LMI), the refund was issued in ETH due to liquidity constraints in buying back the lost tokens. To express appreciation for the affected users' trust and support, MaestroBots increased the refund amount by 20%, resulting in a total cost of 334 ETH. CertiK, a blockchain security firm, verified the transactions, confirming the 334 ETH compensation disbursed to users by MaestroBots. Abbas Abou Daya, CEO of MaestroBots, said: "We absolutely refuse to expose our users to such bad actors, and we needed to do right by the few who were affected. The only right option was refunding every single user to the absolute best of our ability. Every wallet that lost tokens in the router exploit has now received the full amount they lost. Some of you ended up with even bigger bags." Abou Daya further explained the choice to buy and refund tokens for most of the affected tokens, stating: "For 9 out of the 11 exploited tokens, we chose to buy and refund tokens instead of simply sending ETH because it's the most equitable and complete refund we can offer for the incident. This gives full control back to the user (plus you can dump on our buys). We spent 276 ETH to secure our users' tokens. For the other two tokens (JOE and LMI), there simply wasn't enough liquidity to allow us to buy back the lost tokens, so we compensated affected users with the ETH equivalent of their tokens, and boosted that amount by 20% because you deserve it. These refunds cost 334 ETH." Abou Daya went on to highlight the quick response to the incident, stating: "Overall, the full refund campaign concluded a mere 10 hours after the exploit. These refunds cost us a total of 610 ETH (~$1.1M), but it's a small price to pay to ensure your safety and peace of mind." The MaestroBot team is committed to user safety: "Team Maestro apologizes for the error. We hold ourselves to a higher standard. That being said, the exploit was fully shut down within 30 minutes, trading capabilities were restored within 2 hours, and full refunds were issued within 10 hours. Anyone who was affected was made whole. Maestro: Router 2 is now completely safe. We hope that the swiftness of our response, paired with the completeness of the offered refund, can serve as a powerful reminder of our continued commitment to do right by our users." CertiK, a blockchain security firm, confirmed the safety and integrity of Maestro: Router 2 following the swift response and resolution of the incident. About MaestroBots MaestroBots is the leading Telegram bot for cryptocurrency trading, offering a wide range of services across Ethereum, BNB Chain, and Arbitrum networks. The platform prioritizes user security and has shown its commitment to safeguarding user assets by promptly addressing and resolving the recent smart contract exploit. For more information about MaestroBots, please visit https://www.maestrobots.com/ Contact Abbas Abou Daya MaestroBots maestro@gearlay.com This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program . here

MaestroBots Makes Users Whole: Refunds 610 ETH Following Router Exploit

MaestroBots ব্যবহারকারীদের সম্পূর্ণ করে তোলে: রাউটার এক্সপ্লয়েট অনুসরণ করে 610 ETH ফেরত দেয়

MaestroBots macht Benutzer gesund: Erstattet 610 ETH nach Router-Exploit

MaestroBots recupera la integridad de los usuarios: reembolsa 610 ETH tras el exploit del enrutador

MaestroBots rend les utilisateurs entiers : rembourse 610 ETH suite à un exploit de routeur

मेस्ट्रोबॉट्स उपयोगकर्ताओं को संपूर्ण बनाता है: राउटर एक्सप्लॉइट के बाद 610 ईटीएच वापस करता है

MaestroBots がユーザーを完全にする: ルーター悪用後に 610 ETH を返金

MaestroBots는 사용자를 온전하게 만듭니다: 라우터 공격에 따라 610 ETH를 환불합니다.

MaestroBots torna os usuários inteiros: reembolsa 610 ETH após exploração do roteador

MaestroBots спасает пользователей: возвращает 610 ETH после взлома маршрутизатора

MaestroBots Kullanıcıları Bütünleştiriyor: Yönlendirici Saldırısının Ardından 610 ETH'yi İade Ediyor

MaestroBots khiến toàn bộ người dùng: Hoàn lại 610 ETH sau khi khai thác bộ định tuyến

MaestroBots 让用户完整：路由器漏洞后退款 610 ETH

This is the and ardently demanded tutorial about the contract and how to use it with the (UR) to swap or sell tokens. It is also the continuation of the introductory tutorial: . long-awaited Permit2 Uniswap Universal Router How to Buy a Token on the Uniswap Universal Router with Python A Bit of Context After (2015), the standard way to allow a protocol to use your tokens was to it to the token contract and give it an , through a transaction. ERC-20 approve allowance Then, (2020) introduced the concept as a standard to give this allowance using a signed message (thanks to the data signing standard) instead of the approval transaction. This EIP brought some nice like: ERC-2612 permit EIP-712 benefits Simplification: less approvals Gas cost: reduced cost, or even no gas at all Security: approvals include an expiration timestamp and a nonce But because it is built on top of ERC-20, only new (or upgradeable) tokens could enjoy them … Then, (November 2022), which allows signature-based approvals for all tokens, Uniswap released the Permit2 contract along with the Universal Router even if they don’t implement ERC-2612. Tutorial Scope and Target The Permit2 and Universal Router contracts have many features, but we’ll focus only on how to leverage both contracts to swap tokens using signed approvals. More specifically, we’re going to learn how to use the UR function. PERMIT2_PERMIT We finished the introductory tutorial after buying some tokens, so we’ll start from there, and we’ll swap them for some . UNI USDT By the end of this tutorial, you will be able to create a transaction to some tokens from the latest Uniswap router with Python, using . sell Permit2 signature-based approvals Prerequisites This tutorial is intended for developers who are comfortable with Python, the basics of (contracts, ERC20, transactions, gas, etc.), and . Ethereum building transactions with web3.py If not already done, it is also strongly recommended to read the introductory tutorial first ( ) to be familiar with the tools, libraries, and setup we’re going to use here as well. How to Buy a Token on the Uniswap Universal Router with Python Libraries, Tools and Setup In this tutorial, we’re going to use the same libraries and tools as we did in the introductory one, so you can refer to it for installation and setup: Web3.py Uniswap Universal Router Codec Python virtual environment CLI Ganache and npm Node.js You don’t want to learn to swap tokens with actual ones. So you can use either a testnet like or a local fork created with Ganache, which is the solution I’ll use in this tutorial. Sepolia New versions of the Web3.py library and UR SDK have been released in the meantime, so be sure you have the latest ones with the following command: $ pip freeze You should get something like: uniswap-universal-router-decoder==0.9.1
web3==6.11.1 if you have older versions, just update the libraries as usual: $ pip install -U uniswap-universal-router-decoder web3 Launching Ganache We’re going to launch Ganache to fork Ethereum locally at block number 17365005, as we did previously. We’re going to use the same private key and give it 100 ETH (= wei, which is in hexadecimal). 100 * 10**18 0x56bc75e2d63100000 My endpoint address is stored in the environment variable , so the command is: $RPC_ENDPOINT $ ganache --fork.url=$RPC_ENDPOINT --wallet.accounts=0x6c9803151aa5cf420e98dd1afb9db96f0510918cb2249e9858519d47777125c9,0x56bc75e2d63100000 --fork.blockNumber=17365005 Do use the private keys/accounts from these tutorials (or from anywhere) on Mainnet! Everyone could access your fund! NOT Also, if you see some tokens in these accounts on Mainnet (or in any account whose private key is on the web), try to get them: a sweeper bot will steal your gas! NEVER Getting some UNI Tokens We’re going to re-use the script from the previous tutorial and append our new code to have a fully independent script to launch. Make sure the script works and gives you UNI. buy_token.py 368.41333521045374 Swapping tokens And now, the moment you've been waiting for: selling our UNI tokens using the Uniswap Universal Router and the Permit2 contract! Step 1: Approving the Permit2 contract to the UNI one This step is similar to the ERC-20 standard, . It is the step that allows all tokens, even those that don’t implement ERC-2612, to use signature-based approvals. except that you approve the Permit2 contract instead of the router # approve Permit2 to UNI
permit2_address = Web3.to_checksum_address("0x000000000022D473030F116dDEE9F6B43aC78BA3")
permit2_allowance = 2**256 - 1  # max
contract_function = uni_contract.functions.approve(
        permit2_address,
        permit2_allowance
)
trx_params = contract_function.build_transaction(
        {
            "from": account.address,
            "gas": 500_000,
            "maxPriorityFeePerGas": w3.eth.max_priority_fee,
            "maxFeePerGas": 100 * 10**9,
            "type": '0x2',
            "chainId": chain_id,
            "value": 0,
            "nonce": w3.eth.get_transaction_count(account.address),
        }
    )
raw_transaction = w3.eth.account.sign_transaction(trx_params, account.key).rawTransaction
trx_hash = w3.eth.send_raw_transaction(raw_transaction)
print(f"Permit2 UNI approve trx hash: {trx_hash.hex()}") In this tutorial, we give the maximum allowance (2**256 - 1 wei), but depending on your use case, you might want to give less on Mainnet. Checking the allowance we have just approved: print(
        "Permit2 UNI allowance:",
        uni_contract.functions.allowance(account.address, permit2_address).call(),
) You should get: Permit2 UNI allowance: 79228162514264337593543950335 Step 2: Building and Signing the permit message Now, we’re ready to build the swap/sell transaction with a signature-based approval. Let’s start with the permit message. a. Permit2 nonce and allowance For security purposes, the message you need to sign contains a nonce. It is incremented for each permit message you sign. The nonce depends on your account address and on the token and universal router addresses. To know the current Permit2 nonce, allowance, and expiration: permit2_abi = '[{"inputs":[{ ... "type":"function"}]'  # truncated
permit2_contract = w3.eth.contract(address=permit2_address, abi=permit2_abi)
p2_amount, p2_expiration, p2_nonce = permit2_contract.functions.allowance(
        account.address,
        uni_address,
        ur_address
).call()
print(
        "p2_amount, p2_expiration, p2_nonce: ",
        p2_amount,
        p2_expiration,
        p2_nonce,
) For readability sake, I’ve truncated most of the abi, but you can get it from Etherscan, as explained in the previous tutorial. If you have a doubt, you can check the . full tutorial code We haven’t yet given any allowance for Permit2 to the UNI contract, so we expect only zeros: permit2_amount, permit2_expiration, permit2_nonce:  0 0 0 b. Building the signable message The approval message is built as follows: # permit message
allowance_amount = 2**160 - 1  # max/infinite
permit_data, signable_message = codec.create_permit2_signable_message(
        uni_address,
        allowance_amount,
        codec.get_default_expiration(),  # 30 days
        p2_nonce,
        ur_address,
        codec.get_default_deadline(),  # 180 seconds
        chain_id,
    ) Let’s breakdown the command: is the amount you’re happy to approve. Here, we set it to the infinite value: allowance_amount 2**160 - 1 gives the timestamp after which the allowance is not valid anymore. The codec default is at 30 days, but you can set whatever you want in the future: you could set 24h like that: codec.get_default_expiration() codec.get_default_expiration(24 * 3600) : the Permit2 nonce we just got at the previous step. permit2_nonce : the timestamp after which the transaction will not be valid anymore. Default is 180s. codec.get_default_deadline() : 1 for Ethereum, 1337 for Ganache, … chain_id contains the permit message details (basically, the arguments) permit_data codec.create_permit2_signable_message() is the EIP-172 encoded version of the permit message. signable_message c. Signing the message Signing the message is as simple as: signed_message = account.sign_message(signable_message) Step 3: The swap transaction a. Encoding the input data The swap part in the transaction we’re going to send to the Universal Router is very similar to what we learned in the previous tutorial. Now could be a good moment to look into it again and refresh our memory about the method because we’re using it again here: v2_swap_exact_in() # Building the Swap to sell UNI for USDT
usdt_address = Web3.to_checksum_address("0xdac17f958d2ee523a2206206994597c13d831ec7")
usdt_abi = '[{"constant" ... :"Unpause","type":"event"}]'  # truncated
usdt_contract = w3.eth.contract(address=usdt_address, abi=usdt_abi)

amount_in = 100 * 10**18
min_amount_out = 415 * 10**6
path = [uni_address, usdt_address]
encoded_input = (
        codec
        .encode
        .chain()
        .permit2_permit(permit_data, signed_message)
        .v2_swap_exact_in(
                FunctionRecipient.SENDER,
                amount_in,
                min_amount_out,
                path,
                payer_is_sender=True,
        )
        .build(codec.get_default_deadline())
    ) Again, the ABI is truncated: you can get it from Etherscan or from the tutorial full code. Let’s breakdown the command: , , , and have already been explained in the introductory tutorial. codec encode chain() v2_swap_exact_in() build() : Encode the call to the Universal router function , with the previously built arguments: and permit2_permit() PERMIT2_PERMIT permit_data signed_message. : at block , the price of UNI was around $4.19, so we gave a bit of room and asked for a minimum of 415 USDT for our 100 UNI. min_amount_out 17365005 b. Building and sending the transaction And the transaction is built and sent as usual: trx_params = {
        "from": account.address,
        "to": ur_address,
        "gas": 500_000,
        "maxPriorityFeePerGas": w3.eth.max_priority_fee,
        "maxFeePerGas": 100 * 10**9,
        "type": '0x2',
        "chainId": chain_id,
        "value": 0,
        "nonce": w3.eth.get_transaction_count(account.address),
        "data": encoded_input,
}
raw_transaction = w3.eth.account.sign_transaction(trx_params, account.key).rawTransaction
trx_hash = w3.eth.send_raw_transaction(raw_transaction)
print(f"Trx Hash: {trx_hash.hex()}") c. Checking the balances If all goes well, you should have 100 UNI less and a positive USDT balance: # Checking the balances
uni_balance = uni_contract.functions.balanceOf(account.address).call()
print("UNI Balance:", uni_balance / 10**18, "UNI")

usdt_balance = usdt_contract.functions.balanceOf(account.address).call()
print("USDT Balance:", usdt_balance / 10**6, "USDT") UNI Balance: 268.41333521045374 UNI
USDT Balance: 419.503665 USDT d. Checking the new Permit2 allowance # Checking the new Permit2 allowance
p2_amount, p2_expiration, p2_nonce = permit2_contract.functions.allowance(
        account.address,
        uni_address,
        ur_address
).call()
print(
        "p2_amount, p2_expiration, p2_nonce: ",
        p2_amount,
        p2_expiration,
        p2_nonce,
) Now, you should get some values similar to: p2_amount, p2_expiration, p2_nonce:  1461501637330902918203684832716283019655932542975 1700722499 1 As long as and is in the future, you can swap the USDT token; you don’t have to add the method when building your next transaction! p2_amount > 0 p2_expiration permit2_permit(permit_data, signed_message) Conclusion Using the PERMIT2_PERMIT function is the way to authorize the Uniswap Universal Router to swap any ERC-20 tokens, even if they don’t support ERC-2612. The great benefit, compared to the ERC-20 standard, is that you don’t have to approve each and every protocol to the USDT contract if they use the Permit2 contract as well. You just need to include a signed permit message in your transaction. If you made it up to here, congrats !!! You have learnt: How to use the Permit2 contract with the Universal Router to swap a token How to encode and sign a Permit2 permit message In addition, you have: Acquired a better understanding of several important protocols and EIPs Practised what you learnt in the previous tutorial Closing words and disclaimer Now that you have a more advanced knowledge of the UR codec, you can continue to play with the other functions it supports. : I’m the of the Python . This open-source library is a work in progress and does not support all UR functions yet. If you ever experience any issues with it, please open a ticket . And feel free to share what other UR functions you would like to be supported by this SDK. Disclaimer author and maintainer Universal Router SDK here

Python: How to Use Permit2 with the Uniswap Universal Router

Stories, News & Mentions about ROOTER

Rooter’s Stories on HackerNoon

Rooter's News & Mentions