Fix urls

not-so-smart-contracts/cosmos/messages_priority/README.md

@@ -58,5 +58,5 @@ Once a bug in pool's implementation is discovered, attackers and the pool's oper
 
 ## External examples
 
-- [Terra Money's oracle messages were not prioritized](https://cryptorisks.substack.com/p/ust-december-2021) (search for "priority"). It was [fixed with modifications to Tendermint](https://github.com/terra-money/tendermint/commit/6805b4866bdbd6933000eb0e761acbf15edd8ed6).
+- [Terra Money's oracle messages were not prioritized](https://x.com/terra_money/status/1524785058296778752). It was [fixed with modifications to Tendermint](https://github.com/terra-money/tendermint/commit/6805b4866bdbd6933000eb0e761acbf15edd8ed6).
 - [Umee oracle and orchestrator messages were not prioritized](https://github.com/trailofbits/publications/blob/master/reviews/Umee.pdf) (search for finding TOB-UMEE-20 and TOB-UMEE-31).

not-so-smart-contracts/substrate/weights_and_fees/README.md

@@ -47,4 +47,4 @@ On the other hand, if an attacker sends a `useful_amounts` vector that is incred
 # References
 
 - https://docs.substrate.io/main-docs/build/tx-weights-fees/
-- https://docs.substrate.io/reference/how-to-guides/weights/add-benchmarks/
+- https://docs.polkadot.com/develop/parachains/testing/benchmarking/

program-analysis/echidna/advanced/hevm-cheats-to-test-permit.md

@@ -8,7 +8,7 @@
 
 This method presents a new way of allocating allowances, as signatures can be computed off-chain and passed to a contract. It allows a relayer to pay the entire gas fee of the permit transaction in exchange for a fee, enabling completely gasless transactions for a user. Furthermore, this removes the typical `approve() -> transferFrom()` pattern that forces users to send two transactions instead of just one through this new method.
 
-Note that for the permit function to work, a valid signature is needed. This example will demonstrate how we can use [`hevm`'s `sign` cheatcode](https://hevm.dev/ds-test-tutorial.html#supported-cheat-codes) to sign data with a private key. More generally, you can use this cheatcode to test anything that requires valid signatures.
+Note that for the permit function to work, a valid signature is needed. This example will demonstrate how we can use [`hevm`'s `sign` cheatcode](https://hevm.dev/std-test-tutorial.html#supported-cheat-codes) to sign data with a private key. More generally, you can use this cheatcode to test anything that requires valid signatures.
 
 ## Example
 

program-analysis/echidna/advanced/on-using-cheat-codes.md

@@ -14,7 +14,7 @@ Cheat codes are special functions that allow to change the state of the EVM in w
 
 ## Cheat codes available in Echidna
 
-Echidna supports all cheat codes that are available in [hevm](https://github.com/ethereum/hevm). These are documented here: [https://hevm.dev/controlling-the-unit-testing-environment.html#cheat-codes](https://hevm.dev/ds-test-tutorial.html#supported-cheat-codes).
+Echidna supports all cheat codes that are available in [hevm](https://github.com/ethereum/hevm). These are documented here: [https://hevm.dev/controlling-the-unit-testing-environment.html#cheat-codes](https://hevm.dev/std-test-tutorial.html#supported-cheat-codes).
 If a new cheat code is added in the future, Echidna only needs to update the hevm version and everything should work out of the box.
 
 As an example, the `prank` cheat code is able to set the `msg.sender` address in the context of the next external call: