FYTO

fyto

Introduction There is a powerful pattern at the heart of the Yield Protocol. It allows us to instantly integrate smart contracts that do not know each other. It also allows us to create new business features on the blockchain without deploying new smart contracts. It allows us to be flexible and scalable, if careful. I’ll call this pattern Forward Trust. Forward Trust is a combination of two concepts: - , in which a contract allows to batch several calls to itself in a single transaction. Multi call - , in which instead of using `transferFrom` to pull tokens from somewhere, a contract records how much of a given token it holds. When a function in that contract is called, any surplus between the recorded and the actual balances is assumed to belong to the caller. Balance tracking These two concepts can be combined so that basic token operations, complex functions, and external calls to other contracts become a higher-level language in which business features can be created off-chain and then immediately executed on-chain. Forward Trust is a combination of two concepts: Multicall and Balance tracking. The idea is not completely new. , , and many others allow users to compose features that integrate several DeFi protocols to build new features. You also have which is a more generalized version of the same idea. Furucombo Instadapp weiroll I didn’t invent Multicall or Balance Tracking. It is quite possible that I wasn’t the first person either to put these two ideas together. I don’t think that matters either way, my intention is to make this pattern known and help others use it so that as an industry we build better and and faster. My intention also is to share the lessons learned from a year of using this pattern, so that others don’t repeat our mistakes. In explaining Forward Trust as it is implemented for the Yield Protocol, I’ll start by giving an overview of Multicall and in general how to build a router smart contract for composable transactions. Following, I’ll explain how to use the Balance Tracking pattern. I’ll include notes alerting of the risks from an incorrect implementation or operation. Finally, I’ll briefly discuss the impact of Forward Trust with regard to core beliefs in smart contract development.** Here we go, buckle up. Building a Composable Router In building a composable router, we are going to break up our business logic into pieces smaller than a business feature, and we are going to implement some tools to put them back together in any combination. With “business feature”, I mean a feature that makes sense to your users. For the Yield Protocol, we have business features such as “add collateral”, “add collateral and borrow underlying”, “add liquidity to a pool”, and many others. These features often have variants, like “add collateral to a position using an off-chain signature”, “borrow using an ERC1155 as collateral”, or “remove my WETH collateral and send it to me as Ether”. Building each of these features separately would require a lot of time, as you would need to code a smart contract and get it through the several stages of testing, auditing, and deployment. That’s __ __and after adding a handful of features we realized the enormous costs. what we did for Yield v1 In a composable router, we break up our business logic into small pieces Yield v2, on the other hand, has a composable router. We already have more than fifty features and can add more at a much faster pace. There aren’t as many constraints imposed by the smart contracts, because smart contracts don’t have to change as often. The idea behind a composable router is that many business features share parts of their code. Some very basic actions that are repeated often are: Take tokens from a user wallet. Execute an off-chain signature for a token approval. Wrap Ether into WETH. Unwrap Ether into WETH. Some other more complex actions that we still repeat often are things like: Build an empty debt position Manage collateral and debt balances Trade assets in YieldSpace Redeem mature fyTokens Your protocol can surely be broken down in the same way. An example recipe for borrowing fyToken in the Yield Protocol would be built from the actions above as follows: Tx1: [
    build(seriesId, ilkId, salt),                  // Create an empty position
    permit(ilk, ladle, posted, deadline, v, r, s), // Execute an off-chain approval
    transfer(ilk, ilkJoin, posted),                // Take tokens from the caller
    pour(vaultId, ignored, posted, 0),             // Add collateral and borrow
] This recipe combines four of the actions available in the router to offer a finished business feature. There are variants to this that without a composable router would require extra smart contract code. For example, some users cannot sign off-chain approvals. For those, the front end will build this instead. Tx1: token.approve(spender, amount)    // Standalone transaction

Tx2: [
    build(seriesId, ilkId, salt),      // Create an empty position
    transfer(ilk, ilkJoin, posted),    // Take tokens from the caller
    pour(vaultId, ignored, posted, 0), // Add collateral and borrow
] As another example, if the user wants to create a fixed-rate loan they need to sell their fyToken in YieldSpace as they borrow them. The recipe for that would be: Tx1: [
    build(seriesId, ilkId, salt),
    permit(ilk, ladle, posted, deadline, v, r, s),
    transfer(ilk, ilkJoin, posted),
    serve(vaultId, receiver, 0, borrowed, maximumDebt),
] The combinations grow exponentially as we match specific conditions and product offerings. Being able to express only the composing actions makes all the difference. Multicall The idea of batching several function calls in a transaction might have been , but later and succinct implementation for batching. By having a function that accepts an array of encoded function calls, and delegatecalls to itself with each one, we build a batching mechanism. first done by dYdX ENS provided an incredibly elegant function multicall(bytes[] calldata data) external returns(bytes[] memory results) {
    results = new bytes[](data.length);
    for(uint i = 0; i < data.length; i++) {
        (bool success, bytes memory result) = address(this).delegatecall(data[i]);
        require(success);
        results[i] = result;
    }
    return results;
} In this way, all the calls in the batch are executed in the same contract. The genius is in using `delegatecall` to preserve `msg.sender` and other transaction variables, as a regular `call` would overwrite `msg.sender` with the contract receiving the batch.** A batching function accepts an array of encoded function calls and delegatecalls to itself with each one. Coding the basic actions to use within multicall is fairly straightforward, they tend to be of code each: one or two lines /// @dev Execute an ERC2612 permit for the selected token
function permit(
  IERC2612 token, address spender, uint256 amount,
  uint256 deadline, uint8 v, bytes32 r, bytes32 s
  ) external payable {
    token.permit(msg.sender, spender, amount, deadline, v, r, s);
}

/// @dev Take tokens from an user
function transfer(IERC20 token, address receiver, uint128 wad) external payable {
  token.safeTransferFrom(msg.sender, receiver, wad);
} Our router has many more examples of actions that we compose into user features, and more can be added by upgrading the router. Calls to these actions are encoded in a calldata string, and then pushed into an array. The `batch` function reads all these actions and executes them sequentially.  A router built this way is very simple and therefore robust, because the actions are small and there is little nesting between them. Just be careful with known ways of . misuse When we released Yield Protocol v2, we knew of a few features we wanted to build, but we also knew that we would regularly think of new features, and that deploying new smart contract code for each one would slow us down. Coding common actions as small individual functions, and using Multicall to put larger business features together from the frontend, we could build much faster. Route We soon realized that we could treat calls to other contracts as building blocks in this language. The Yield Protocol contains an automated market maker, YieldSpace, which acts as a permisionless unit on its own. By implementing a in our router, which simply calls a function on any other contract using `call`, we could use a single function in the router to call any function on a YieldSpace pool. We soon extended that so that we could call any contract from the router. `route` building block The challenge we faced is that our router has permissions on some other contracts .If we allowed anyone to execute arbitrary calls from our router we would effectively allow them to impersonate our router, with catastrophic results. We can call any function in any contract from the router We saw several solutions for this problem: - Make sure the contract implementing `route` never has permissions anywhere. - Implement a blacklist of contracts that calls cannot be routed to. - Install a relayer to `route` calls through, and make sure the relayer never has permissions anywhere. We implemented both a relayer and a whitelist of contracts that we could route calls to, for added security. There is no simple best solution, but the lesson is that you can include simple calls to contracts as yet unknown as one of the actions in your router. There were risks in allowing arbitrary calls from our router, but time has shown that the extra flexibility makes it worth it. Token Transfers Closer to the go-live, when we were busy creating feature after feature, I noticed that it was much easier to integrate with our YieldSpace pools than with other contracts. That was because YieldSpace was modeled after , and it tracked its own balances. When you wanted to sell Dai, you could send a transfer the Dai to the YieldSpace Pool contract, and then call the `sell` function there on the same transaction. The pool would check its Dai balance against the recorded reserves and would find that there was a surplus of Dai. Then it assumed the Dai was yours and executed the sale. Uniswap v2 The extra storage required to track balances might seem like a waste, but in exchange, the caller doesn't need to approve the pool to take tokens. The caller doesn’t need to know much about what will happen to the tokens, no more approvals needed. You might not be impressed. The whole approve and transferFrom pattern is annoying, but it works, so what's the deal? The deal is that with this pattern the caller doesn’t need to know much about what will happen to the tokens, only that they need to be dropped somewhere. If we are building transactions as a batch each function, perhaps in a different contract, follows a simple pattern: Check what the input was Do something with the input Leave the output somewhere Update recorded balances No more approvals are needed. Each function does its thing and drops tokens in some other contract. The next contract to be called by the `batch` function finds out how many tokens he just received, and continues the execution. Just make sure that every token transfer inside a function has its own parameter for a receiver, . you’ll thank me later Suddenly, you can scale. It doesn't matter anymore how many contracts you have in your protocol. Everyone is integrated with everyone else out of the box. Even with contracts that don't exist yet. Here be dragons Now that we have discussed the advantages of Forward Trust, we must discuss the risks. Everything always has its trade-offs, and the strength of the advantages implies the disadvantages are serious as well. You must tread lightly. The Dark Forest When you implement your contracts according to this pattern, you need to be very aware that you are entering . Bots lurk in it and will take any tokens if they can. the dark forest When building the contracts, you need to be careful about how you track the balances, and how the tokens can leave the contract. If the surplus is not calculated correctly, anyone will take what they can. When building recipes, ensure that you don’t leave tokens unattended when your transaction ends. If you send tokens somewhere and don't call the recipient so that it uses them or updates its balances, they will vanish. Be aware that you are entering the Dark Forest When communicating with your users, you need to stress that just calling functions on Etherscan is not as safe as they are used to. They can’t hurt your protocol, but they are likely to lose their funds. You can use this pattern, and we have done so safely for a year at Yield, but be aware that you need to think differently now. Tales from the front The recipes to execute business features within the Yield Protocol are complex. They could be three, four, or maybe eight function calls batched with very precise parameters. Users only see an innocent-looking button, but a lot of work is required to make sure that a recipe is safe. Using Forward Trust, the business experts build the recipes with help from smart contract developers. Then the frontend takes the enormous responsibility of implementing them correctly and testing them again to make sure they work as intended. The frontend developers take an equal responsibility There is a big shift in risk from the smart contract developers to the frontend developers, as only the frontend now protects the users against bots. You need to apply the same level of attention to your frontend and to your smart contracts. Trust, but verify There is a tradition of giving users complete visibility into how a smart contract works. Trust, but verify. By shifting development towards the frontend Forward Trust makes verification more difficult, unfortunately. Frontend code is often private, as a moat protecting against protocol forks. Frontends could be updated at any time with new code that changes the recipes, maybe with bad consequences for the users. There are some calls to provide decentralized and verifiable frontends, and they are even more necessary using this pattern. Shifting development towards the frontend makes verification more difficult Transactions are not private, though, and they can be previewed and debugged. Tools like__ __ make it easy to see the effects of any transaction before it gets executed, and user communities could use it to verify frontend implementations and point out inconsistencies. Tenderly Conclusion The is built differently. Using Multicall and the idea of tracking token balances, we built a higher-level language to create business products with. The result was a very flexible and scalable protocol, but that came with its own set of challenges. Yield Protocol We didn't do what the auditors expected of us, and we had to figure out ways to use this pattern safely. Sometimes we made mistakes and learned from them. One year later, we are still alive, and pumping out features at a fierce rate. It's paying off. I hope that you learned something useful from this article. Maybe you’ll get to code better applications on the blockchain, more powerful and flexible. Be careful of the risks while we come up with better ways of managing them. Good luck. Thanks to whoever came up with Multicall first, I’m guessing that Nick Johnson. Thanks to Uniswap for coming up with Balance Tracking. Thanks to BoringSolidity who I based my own Multicall implementation on. Thanks to Allan Niemerg for giving me the opportunity to build the Yield Protocol. Thanks to transmissions11 and sorry I didn’t name the pattern as you suggested. Thanks to everyone who has helped me build and learn, there are lots of you.

Using the Forward Trust Design Pattern to Make Scaling Easier

The Gambler by Fyodor Dostoyevsky is part of the HackerNoon Books Series. Read this book online for free on HackerNoon! : The Gambler Title : Fyodor Dostoyevsky Author : C. J. Hogarth Translator : May 1, 2000 [eBook #2197] Most recently updated: June 30, 2020 Release date : English Language Table of Links Chapter I Chapter II Chapter III Chapter IV Chapter V Chapter VI Chapter VII Chapter VIII Chapter IX Chapter X Chapter XI Chapter XII Chapter XIII Chapter XIV Chapter XV Chapter XVI Chapter XVII 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. Fyodor Dostoyevsky (2000). The Gambler. Urbana, Illinois: Project Gutenberg. Retrieved https://www.gutenberg.org/cache/epub/2197/pg2197-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 Gambler by Fyodor Dostoyevsky - Table of Links

White Nights and Other Stories by Fyodor Dostoyevsky is part of the HackerNoon Books Series. Read this book online for free on HackerNoon! : White Nights and Other Stories Title : Fyodor Dostoyevsky Author : Constance Garnett Translator : May 5, 2011 [eBook #36034] Release date : English Language TABLE OF LINKS White Nights Notes from Underground— part i. underground part ii. à propos of the wet snow A Faint Heart A Christmas Tree and a Wedding Polzunkov A Little Hero Mr. Prohartchin 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. Fyodor Dostoyevsky (2011). White Nights and Other Stories. Urbana, Illinois: Project Gutenberg. Retrieved October https://www.gutenberg.org/cache/epub/36034/pg36034-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.

White Nights and Other Stories by Fyodor Dostoyevsky - Table of Links

Poor Folk by Fyodor Dostoyevsky is part of the HackerNoon Books Series. Read this book online for free on HackerNoon! : Poor Folk Title : Fyodor Dostoyevsky Author : C. J. Hogarth Translator : August 1, 2000 [eBook #2302] Most recently updated: February 26, 2021 Release date : English Language Table of Links April 8th April 8th April 8th April 9th April 12th April 25th May 20th June 1st June 11th June 12th. June 20th. June 21st. June 22nd. June 25th. June 26th. June 27th. June 28th. July 1st. July 7th. July 8th. July 27th. July 28th. July 28th. July 29th. August 1st. August 2nd. August 3rd. August 4th. August 4th. August 5th. August 5th. August 11th. August 13th. August 14th. August 19th. August 21st. September 3rd. September 5th. September 9th. September 10th. September 11th. September 15th. September 18th. September 19th. September 23rd. September 23rd. September 27th. September 27th. September 28th. September 28th. September 29th. September 30th 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. Fyodor Dostoyevsky (2000). Poor Folk. Urbana, Illinois: Project Gutenberg. Retrieved October https://www.gutenberg.org/cache/epub/2302/pg2302-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 .

Poor Folk by Fyodor Dostoyevsky - Table of Links

Short Stories by Fyodor Dostoyevsky is part of the HackerNoon Books Series. Read this book online for free on HackerNoon! : Short Stories Title : Fyodor Dostoyevsky Author : September 13, 2012 [eBook #40745] Release date : English Language Table of Links An Honest Thief A Novel in Nine Letters An Unpleasant Predicament Another Man's Wife The Heavenly Christmas Tree The Peasant Marey The Crocodile Bobok The Dream of a Ridiculous Man 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. Fyodor Dostoyevsky (2012).Short Stories. Urbana, Illinois: Project Gutenberg. Retrieved October https://www.gutenberg.org/cache/epub/40745/pg40745-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

Short Stories by Fyodor Dostoyevsky - Table of Links

The Possessed (The Devils) by Fyodor Dostoyevsky is part of the HackerNoon Books Series. Read this book online for free on HackerNoon! : The Possessed (The Devils) Title : Fyodor Dostoyevsky : Constance Garnett Author Translator : May 1, 2005 [eBook #8117] Most recently updated: July 5, 2017 Release date : English Language Table of Links PART I. CHAPTER I. INTRODUCTORY CHAPTER II. PRINCE HARRY. MATCHMAKING CHAPTER III. THE SINS OF OTHERS CHAPTER IV. THE CRIPPLE CHAPTER V. THE SUBTLE SERPENT PART II. CHAPTER I. NIGHT CHAPTER II. NIGHT (continued) CHAPTER III. THE DUEL CHAPTER IV. ALL IN EXPECTATION CHAPTER V. ON THE EVE OF THE FETE CHAPTER VI. PYOTR STEPANOVITCH IS BUSY CHAPTER VII. A MEETING CHAPTER VIII. IVAN THE TSAREVITCH CHAPTER IX. A RAID AT STEPAN TROFIMOVITCH’S CHAPTER X. FILIBUSTERS. A FATAL MORNING PART III. CHAPTER I. THE FETE—FIRST PART CHAPTER II. THE END OF THE FETE CHAPTER III. A ROMANCE ENDED CHAPTER IV. THE LAST RESOLUTION CHAPTER V. A WANDERER CHAPTER VI. A BUSY NIGHT CHAPTER VII. STEPAN TROFIMOVITCH’S LAST WANDERING CHAPTER VIII. CONCLUSION 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. Fyodor Dostoyevsky (2005). The Possessed (The Devils). Urbana, Illinois: Project Gutenberg. Retrieved October https://www.gutenberg.org/cache/epub/8117/pg8117-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 Possessed (The Devils) by Fyodor Dostoyevsky - Table of Links

Notes from the Underground by Fyodor Dostoyevsky is part of the HackerNoon Books Series. Read this book online for free on HackerNoon! : Notes from the Underground Title : Fyodor Dostoyevsky Author : July 1, 1996 [eBook #600] Most recently updated: December 26, 2021 Release date : English Language Table of Links PART I Underground I II III IV V VI VII VIII IX X XI PART II À Propos of the Wet Snow I II III IV V VI VII VIII IX X 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. Fyodor Dostoyevsky (1996). Notes from the Underground. Urbana, Illinois: Project Gutenberg. Retrieved October https://www.gutenberg.org/cache/epub/600/pg600-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.

Notes from the Underground by Fyodor Dostoyevsky - Table of Links

The House of the Dead; or, Prison Life in Siberia by Fyodor Dostoyevsky is part of the HackerNoon Books Series. Read this book online for free on HackerNoon! : The House of the Dead; or, Prison Life in Siberia Title : Fyodor Dostoyevsky Author : September 25, 2011 [eBook #37536] Release date : English Language Table of Links INTRODUCTION PART I CHAPTER I.  Ten Years a Convict II.  The Dead-House III.  First Impressions IV.  First Impressions (continued) V.  First Impressions (continued) VI.  The First Month VII.  The First Month (continued) VIII.  New Acquaintances—Petroff IX.  Men of Determination—Luka X.  Isaiah Fomitch—The Bath—Baklouchin XI.  The Christmas Holidays XII.  The Performance PART II I.  The Hospital II.  The Hospital (continued) III.  The Hospital (continued) IV.  The Husband of Akoulka V.  The Summer Season VI.  The Animals at the Convict Establishment VII.  Grievances VIII.  My Companions IX.  The Escape X.  Freedom! 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. Fyodor Dostoyevsky (2011). The House of the Dead; or, Prison Life in Siberia. Urbana, Illinois: Project Gutenberg. Retrieved October https://www.gutenberg.org/cache/epub/37536/pg37536-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 House of the Dead; or, Prison Life in Siberia by Fyodor Dostoyevsky - Table of Links

The Brothers Karamazov by Fyodor Dostoyevsky is part of the HackerNoon Books Series. Read this book online for free on HackerNoon! : The Brothers Karamazov Title : Fyodor Dostoyevsky Author : Constance Garnett Translator : February 12, 2009 [eBook #28054] Most recently updated: January 22, 2023 Release date : English Language Table of Links Part I Book I. The History Of A Family Chapter I. Fyodor Pavlovitch Karamazov Chapter II. He Gets Rid Of His Eldest Son Chapter III. The Second Marriage And The Second Family Chapter IV. The Third Son, Alyosha Chapter V. Elders Book II. An Unfortunate Gathering Chapter I. They Arrive At The Monastery Chapter II. The Old Buffoon Chapter III. Peasant Women Who Have Faith Chapter IV. A Lady Of Little Faith Chapter V. So Be It! So Be It! Chapter VI. Why Is Such A Man Alive? Chapter VII. A Young Man Bent On A Career Chapter VIII. The Scandalous Scene Book III. The Sensualists Chapter I. In The Servants’ Quarters Chapter II. Lizaveta Chapter III. The Confession Of A Passionate Heart—In Verse Chapter IV. The Confession Of A Passionate Heart—In Anecdote Chapter V. The Confession Of A Passionate Heart—“Heels Up” Chapter VI. Smerdyakov Chapter VII. The Controversy Chapter VIII. Over The Brandy Chapter IX. The Sensualists Chapter X. Both Together Chapter XI. Another Reputation Ruined Part II Book IV. Lacerations Chapter I. Father Ferapont Chapter II. At His Father’s Chapter III. A Meeting With The Schoolboys Chapter IV. At The Hohlakovs’ Chapter V. A Laceration In The Drawing‐Room Chapter VI. A Laceration In The Cottage Chapter VII. And In The Open Air Book V. Pro And Contra Chapter I. The Engagement Chapter II. Smerdyakov With A Guitar Chapter III. The Brothers Make Friends Chapter IV. Rebellion Chapter V. The Grand Inquisitor Chapter VI. For Awhile A Very Obscure One Chapter VII. “It’s Always Worth While Speaking To A Clever Man” Book VI. The Russian Monk Chapter I. Father Zossima And His Visitors Chapter II. The Duel Chapter III. Conversations And Exhortations Of Father Zossima Part III Book VII. Alyosha Chapter I. The Breath Of Corruption Chapter II. A Critical Moment Chapter III. An Onion Chapter IV. Cana Of Galilee Book VIII. Mitya Chapter I. Kuzma Samsonov Chapter II. Lyagavy Chapter III. Gold‐Mines Chapter IV. In The Dark Chapter V. A Sudden Resolution Chapter VI. “I Am Coming, Too!” Chapter VII. The First And Rightful Lover Chapter VIII. Delirium Book IX. The Preliminary Investigation Chapter I. The Beginning Of Perhotin’s Official Career Chapter II. The Alarm Chapter III. The Sufferings Of A Soul, The First Ordeal Chapter IV. The Second Ordeal Chapter V. The Third Ordeal Chapter VI. The Prosecutor Catches Mitya Chapter VII. Mitya’s Great Secret. Received With Hisses Chapter VIII. The Evidence Of The Witnesses. The Babe Chapter IX. They Carry Mitya Away Part IV Book X. The Boys Chapter I. Kolya Krassotkin Chapter II. Children Chapter III. The Schoolboy Chapter IV. The Lost Dog Chapter V. By Ilusha’s Bedside Chapter VI. Precocity Chapter VII. Ilusha Book XI. Ivan Chapter I. At Grushenka’s Chapter II. The Injured Foot Chapter III. A Little Demon Chapter IV. A Hymn And A Secret Chapter V. Not You, Not You! Chapter VI. The First Interview With Smerdyakov Chapter VII. The Second Visit To Smerdyakov Chapter VIII. The Third And Last Interview With Smerdyakov Chapter IX. The Devil. Ivan’s Nightmare Chapter X. “It Was He Who Said That” Book XII. A Judicial Error Chapter I. The Fatal Day Chapter II. Dangerous Witnesses Chapter III. The Medical Experts And A Pound Of Nuts Chapter IV. Fortune Smiles On Mitya Chapter V. A Sudden Catastrophe Chapter VI. The Prosecutor’s Speech. Sketches Of Character Chapter VII. An Historical Survey Chapter VIII. A Treatise On Smerdyakov Chapter IX. The Galloping Troika. The End Of The Prosecutor’s Speech. Chapter X. The Speech For The Defense. An Argument That Cuts Both Ways Chapter XI. There Was No Money. There Was No Robbery Chapter XII. And There Was No Murder Either Chapter XIII. A Corrupter Of Thought Chapter XIV. The Peasants Stand Firm Epilogue Chapter I. Plans for Mitya’s Escape Chapter II. For A Moment the Lie Becomes Truth Chapter III. Ilusha’s Funeral. The Speech at the Stone 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. Fyodor Dostoyevsky (2009). The Brothers Karamazov. Urbana, Illinois: Project Gutenberg. Retrieved October https://www.gutenberg.org/cache/epub/28054/pg28054-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 Brothers Karamazov by Fyodor Dostoyevsky - Table of Links

The Brothers Karamazov by Fyodor Dostoyevsky is part of the HackerNoon Books Series. You can jump to any chapter in this book here . Fyodor Pavlovitch Karamazov Chapter I. Fyodor Pavlovitch Karamazov Alexey Fyodorovitch Karamazov was the third son of Fyodor Pavlovitch Karamazov, a land owner well known in our district in his own day, and still remembered among us owing to his gloomy and tragic death, which happened thirteen years ago, and which I shall describe in its proper place. For the present I will only say that this “landowner”—for so we used to call him, although he hardly spent a day of his life on his own estate—was a strange type, yet one pretty frequently to be met with, a type abject and vicious and at the same time senseless. But he was one of those senseless persons who are very well capable of looking after their worldly affairs, and, apparently, after nothing else. Fyodor Pavlovitch, for instance, began with next to nothing; his estate was of the smallest; he ran to dine at other men’s tables, and fastened on them as a toady, yet at his death it appeared that he had a hundred thousand roubles in hard cash. At the same time, he was all his life one of the most senseless, fantastical fellows in the whole district. I repeat, it was not stupidity—the majority of these fantastical fellows are shrewd and intelligent enough—but just senselessness, and a peculiar national form of it. He was married twice, and had three sons, the eldest, Dmitri, by his first wife, and two, Ivan and Alexey, by his second. Fyodor Pavlovitch’s first wife, Adelaïda Ivanovna, belonged to a fairly rich and distinguished noble family, also landowners in our district, the Miüsovs. How it came to pass that an heiress, who was also a beauty, and moreover one of those vigorous, intelligent girls, so common in this generation, but sometimes also to be found in the last, could have married such a worthless, puny weakling, as we all called him, I won’t attempt to explain. I knew a young lady of the last “romantic” generation who after some years of an enigmatic passion for a gentleman, whom she might quite easily have married at any moment, invented insuperable obstacles to their union, and ended by throwing herself one stormy night into a rather deep and rapid river from a high bank, almost a precipice, and so perished, entirely to satisfy her own caprice, and to be like Shakespeare’s Ophelia. Indeed, if this precipice, a chosen and favorite spot of hers, had been less picturesque, if there had been a prosaic flat bank in its place, most likely the suicide would never have taken place. This is a fact, and probably there have been not a few similar instances in the last two or three generations. Adelaïda Ivanovna Miüsov’s action was similarly, no doubt, an echo of other people’s ideas, and was due to the irritation caused by lack of mental freedom. She wanted, perhaps, to show her feminine independence, to override class distinctions and the despotism of her family. And a pliable imagination persuaded her, we must suppose, for a brief moment, that Fyodor Pavlovitch, in spite of his parasitic position, was one of the bold and ironical spirits of that progressive epoch, though he was, in fact, an ill‐natured buffoon and nothing more. What gave the marriage piquancy was that it was preceded by an elopement, and this greatly captivated Adelaïda Ivanovna’s fancy. Fyodor Pavlovitch’s position at the time made him specially eager for any such enterprise, for he was passionately anxious to make a career in one way or another. To attach himself to a good family and obtain a dowry was an alluring prospect. As for mutual love it did not exist apparently, either in the bride or in him, in spite of Adelaïda Ivanovna’s beauty. This was, perhaps, a unique case of the kind in the life of Fyodor Pavlovitch, who was always of a voluptuous temper, and ready to run after any petticoat on the slightest encouragement. She seems to have been the only woman who made no particular appeal to his senses. Immediately after the elopement Adelaïda Ivanovna discerned in a flash that she had no feeling for her husband but contempt. The marriage accordingly showed itself in its true colors with extraordinary rapidity. Although the family accepted the event pretty quickly and apportioned the runaway bride her dowry, the husband and wife began to lead a most disorderly life, and there were everlasting scenes between them. It was said that the young wife showed incomparably more generosity and dignity than Fyodor Pavlovitch, who, as is now known, got hold of all her money up to twenty‐five thousand roubles as soon as she received it, so that those thousands were lost to her for ever. The little village and the rather fine town house which formed part of her dowry he did his utmost for a long time to transfer to his name, by means of some deed of conveyance. He would probably have succeeded, merely from her moral fatigue and desire to get rid of him, and from the contempt and loathing he aroused by his persistent and shameless importunity. But, fortunately, Adelaïda Ivanovna’s family intervened and circumvented his greediness. It is known for a fact that frequent fights took place between the husband and wife, but rumor had it that Fyodor Pavlovitch did not beat his wife but was beaten by her, for she was a hot‐tempered, bold, dark‐browed, impatient woman, possessed of remarkable physical strength. Finally, she left the house and ran away from Fyodor Pavlovitch with a destitute divinity student, leaving Mitya, a child of three years old, in her husband’s hands. Immediately Fyodor Pavlovitch introduced a regular harem into the house, and abandoned himself to orgies of drunkenness. In the intervals he used to drive all over the province, complaining tearfully to each and all of Adelaïda Ivanovna’s having left him, going into details too disgraceful for a husband to mention in regard to his own married life. What seemed to gratify him and flatter his self‐love most was to play the ridiculous part of the injured husband, and to parade his woes with embellishments. “One would think that you’d got a promotion, Fyodor Pavlovitch, you seem so pleased in spite of your sorrow,” scoffers said to him. Many even added that he was glad of a new comic part in which to play the buffoon, and that it was simply to make it funnier that he pretended to be unaware of his ludicrous position. But, who knows, it may have been simplicity. At last he succeeded in getting on the track of his runaway wife. The poor woman turned out to be in Petersburg, where she had gone with her divinity student, and where she had thrown herself into a life of complete emancipation. Fyodor Pavlovitch at once began bustling about, making preparations to go to Petersburg, with what object he could not himself have said. He would perhaps have really gone; but having determined to do so he felt at once entitled to fortify himself for the journey by another bout of reckless drinking. And just at that time his wife’s family received the news of her death in Petersburg. She had died quite suddenly in a garret, according to one story, of typhus, or as another version had it, of starvation. Fyodor Pavlovitch was drunk when he heard of his wife’s death, and the story is that he ran out into the street and began shouting with joy, raising his hands to Heaven: “Lord, now let test Thou Thy servant depart in peace,” but others say he wept without restraint like a little child, so much so that people were sorry for him, in spite of the repulsion he inspired. It is quite possible that both versions were true, that he rejoiced at his release, and at the same time wept for her who released him. As a general rule, people, even the wicked, are much more naïve and simple‐hearted than we suppose. And we ourselves are, too. 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. Fyodor Dostoyevsky (2009). The Brothers Karamazov. Urbana, Illinois: Project Gutenberg. Retrieved October https://www.gutenberg.org/cache/epub/28054/pg28054-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 .

Stories, News & Mentions about FYTO

Fyto’s Stories on HackerNoon