Crates.io | loam-subcontract-core |
lib.rs | loam-subcontract-core |
version | |
source | src |
created_at | 2024-05-23 14:40:49.354796 |
updated_at | 2025-01-22 19:09:38.246462 |
description | Core Subcontract for redeployable contracts |
homepage | |
repository | https://github.com/loambuild/loam/tree/main/crates/loam-subcontract-core |
max_upload_size | |
id | 1249589 |
Cargo.toml error: | TOML parse error at line 17, column 1 | 17 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
Contains the trait and implementation of the Core Subcontract, which contains core functionality needed by every Loam smart contract:
redeploy
: Loam's subcontract pattern is built with upgradeability in mind. Every Loam smart contract gets a redeploy
method, thanks to loam-subcontract-core
, that allows it to be updated with new logic.admin_get
and admin_set
: you want to make sure only the admin (you, probably, to start out) can call redeploy
on your contract, to avoid attackers upgrading to a contract definition that kicks you out.For more information about how to use and author Subcontracts, see the loam-sdk README.