openzeppelin-contracts-upgradeable
plutus
Our great sponsors
| openzeppelin-contracts-upgradeable | plutus | |
|---|---|---|
| 10 | 89 | |
| 933 | 1,532 | |
| 1.4% | 3.6% | |
| 9.4 | 9.8 | |
| 10 days ago | 4 days ago | |
| JavaScript | Haskell | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
openzeppelin-contracts-upgradeable
-
Solidity digest / mar 2023
v4.8.2 of OpenZeppelin contracts and contracts-upgradeable bug fix for ERC721Consecutive that could cause a balance overflow when _mintConsecutive was used for batches of size 1 breaking changes to ERC721: the internal function _beforeTokenTransfer will no longer update balances when batchSize is greater than 1
- Issue logging out certain state variables in Hardhat
-
Can a function that implements __Ownable_init by not with the initializable modifier be run more than once?
Yeah. That restriction is coming from a utility. There are options to modify the owner through transfer ownership on the `OwnableUpgradable` contract. You can also use the `reinitializer' modifier to create your own re-init logic.
- Contract inheritance is a reason Open Zeppelin plans to adopt Diamond Storage
-
Nuances of Using Upgradeable Smart Contracts
Most smart contracts developers have used Openzeppelin/contracts. Those developers dabbling in Upgradeable smart contracts use its sister project Openzeppelin/contracts-upgradeable. The two are the same albeit the constructor in the contract is replaced by the initializer.
-
Contract example with best practices?
Here’s a few references: - https://openzeppelin.com/contracts/ - https://github.com/OpenZeppelin/openzeppelin-contracts-upgradeable (highly recommended)
- Token
-
It costs $436 to deploy a smartcontract on Ethereum
https://github.com/OpenZeppelin/openzeppelin-contracts-upgra...
For KYC you'll need to implement your own ERC20 compatible token with some checks in the transfer functions. The CMTA is the Swiss contract reference and proposes one:
- https://np.reddit.com/r/solidity/comments/prlgj8/how_do_we_create_an_upgradeable_smart_contract/hdjnhnd/
- How do we create an upgradeable smart contract with a hardhat?
plutus
-
Are you disappointed/happy with current daps?
Plutus-related issues in Plutus repo https://github.com/input-output-hk/plutus/issues Cardano node-related issues in the Cardano node repo https://github.com/input-output-hk/cardano-node
-
A Comprehensive Guide on Web3 Programming Languages and Tools
Plutus (Haskell) is a statically typed programming language wired for writing reliable smart contracts on the Cardano blockchain. It is also a functional programming language, which means programs are composed as sets of mathematical functions for execution.
-
Software Development Languages: Haskell
* https://github.com/input-output-hk/plutus
There's quite a few recent Isabelle repos such as https://github.com/input-output-hk/high-assurance-legacy
I haven't worked there for a year or so and don't remember specifics like KLOCs, just that they're dotted around internal and public repos :)
-
Liqwid Labs: Technical Status Update #51
PR for Improved Rational for on-chain size was merged into Plutus: https://github.com/input-output-hk/plutus/commit/6d8d25d1e84b2a4278da1036aab23da4161b8df8
-
Cardano vs. Ethereum: Can Ada Solve Ether’s Problems?
Cardano also suffers from the issue of the size of Plutus script being too big. One script can eat up to 20% of block which renders the overall efficiency even worse.
- Cardano: "Slow and Steady wins the... Annnnnd it's gone." Plutus auditor publicly announces that most Cardano smart contracts have an exploit.
-
Why Cardano smart contract transactions are so big.
They're working on script libraries where you can reference a script in another UTXO rather than having to reinclude it every time. This is mentioned in some videos (I think in November's mid month update and Cardano 360), if you don't have time to watch those it's mentioned in michaelpj's comment here along with some other optimisations they're working on https://github.com/input-output-hk/plutus/issues/4174
-
Why does the same smart contract need to be included with every utxo?
There is a discussion on GitHub about this. The second solution in MPJs reply is what you are suggesting.
- PAB release date?
-
Why all the hate?
About to say that lol. Here are more info.https://plutus-apps.readthedocs.io/en/latest/index.htmlhttps://github.com/input-output-hk/plutushttps://docs.cardano.org/plutus/learn-about-plutus
What are some alternatives?
openzeppelin-contracts - OpenZeppelin Contracts is a library for secure smart contract development.
marlowe - Prototype implementation of domain-specific language for the design of smart-contracts over cryptocurrencies
smart-contract-best-practices - A guide to smart contract security best practices
reach-lang - Reach: The Safest and Smartest DApp Programming Language
cardano-node - The core component that is used to participate in a Cardano decentralised blockchain.
l2beat - L2BEAT is an analytics and research website about Ethereum layer two (L2) scaling solutions.
plutus-pioneer-program - This repository hosts the lectures of the Plutus Pioneers Program. This program is a training course that the IOG Education Team provides to recruit and train software developers in Plutus, the native smart contract language for the Cardano ecosystem.
fe - Emerging smart contract language for the Ethereum blockchain.
plutus-starter - A starter project for Plutus apps
openzeppelin-contracts-upgra