Is that really that hard though? It does require a price oracle but otherwise it's a pretty easy limit to set.
> If you're wrong, the bridge will freeze right when a lot of people want to use it.
I mean, this stuff should be staying in beta a LOT longer than it is, and in a nice long beta you could be increasing limits gradually.
The parent commenter is referencing several fields:
> Sybil attack: https://www.sciencedirect.com/topics/computer-science/sybil-....
This is a type of peer-to-peer strategic attack. So you could postulate that this broadly falls under the category of "common p2p network attacks and vulnerabilities". Google that!
> Circuit breaker: https://en.wikipedia.org/wiki/Circuit_breaker_design_pattern
This is a type of software pattern for making sure a signal (usually bad) doesn't keep recurring and its blast radius is contained.
> Now you're basically trying to devise a heuristic of what every single attack might look like in terms of transaction volume increase. If you're wrong, the bridge will freeze right when a lot of people want to use it. Plus, you also need to build a price oracle now.
This is blockchain specific, but you can definitely deep dive into how blockchains work to get to a point where you understand the concept of a "bridge", "price oracle", etc.
All this said, some people are more breadth-first-search learners, so, if you find yourself in a situation where this is overwhelming but you still want to know, you can always start teaching yourself fundamentals that lead to these areas. I'm roughly breaking down the stack for you here:
First stack: * intro to programming (and getting deep into programming in general) * understanding the basics of an CRUD database app (client-server systems) * understanding multiple services (microservices and systems architecture) * distributed systems (consensus algos, time drift + vector clocks, etc.) * specialization in understanding the blockchain data structure * specialization in understanding p2p systems and their faults
Circuit breakers based on price/volume/volatility is standard finance tech.
With that said smart-contract programming is (at least for now) an in-demand skill set.
The company I work for is interested in developing that skill set because such people are in short supply. A background in conventional distributed systems is very helpful, but anyone with a solid grounding in CS fundamentals can pick it up. It’s a different execution cost model and it’s an adversarial environment, so one needs to keep their wits about them, but it’s learnable like anything.
If you want to know more: [email protected]
* The solidity docs are very good - dry and daunting but not too bad to get through.
* Ethernaut has some great CTFs you can play with.
Also some other books: Mastering Bitcoin Mastering Eth The Sovereign individual
Then i would read the first 10 chapters of the rust book, then dive into substrate.
Easier said than done. This is obviously vulnerable to sybil attack- the attacker just make a lot of different transactions. You could build in a circuit breaker that would slow down transactions to only allow a certain rate of increase in total dollar volume going through the bridge. Hopefully this would slow the attacker down enough.
Now you're basically trying to devise a heuristic of what every single attack might look like in terms of transaction volume increase. If you're wrong, the bridge will freeze right when a lot of people want to use it. Plus, you also need to build a price oracle now.
All of this is possible, but maybe it's better to spend that effort on just making sure the code is secure in the first place.