internet-court/internet-court-skill / vendored/near/near-smart-contracts
near-smart-contracts
FlaggedNEAR Protocol smart contract development in Rust. Use when writing, reviewing, or deploying NEAR smart contracts. Covers contract structure, state management, cross-contract calls, testing, security, and optimization patterns. Based on near-sdk v5.x with modern macro syntax.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 329 B |
| SKILL.md | skill md | 13.9 KB |
| rules/best-contract-tools.md | markdown | 11.4 KB |
| rules/chain-signatures.md | markdown | 12.5 KB |
| rules/security-storage-checks.md | markdown | 3.5 KB |
| rules/state-collections.md | markdown | 4.0 KB |
| rules/structure-near-bindgen.md | markdown | 2.9 KB |
| rules/testing-integration-tests.md | markdown | 5.7 KB |
| rules/upgrade-migration.md | markdown | 4.9 KB |
| rules/xcc-promise-chaining.md | markdown | 4.7 KB |
| rules/yield-resume.md | markdown | 8.3 KB |
rules/structure-near-bindgen.md
View on GitHub# Structure: NEAR Contract Macros
Use `#[near(contract_state)]` macro for contract struct and `#[near]` for implementation blocks.
## Why It Matters
The NEAR macros are essential for smart contracts as they:
- Automatically handle Borsh serialization/deserialization
- Expose methods to the NEAR runtime
- Manage contract state lifecycle
- Enable proper initialization patterns
## ❌ Incorrect
```rust
// Missing NEAR macros - contract won't work
pub struct Contract {
pub owner: AccountId,
pub data: IterableMap<AccountId, String>,
}
impl Contract {
pub fn new(owner: AccountId) -> Self {
Self {
owner,
data: IterableMap::new(b"d"),
}
}
}
```
**Problems:**
- Contract methods won't be callable
- State won't be properly serialized
- Runtime won't recognize the contract
- No initialization validation
## ✅ Correct
```rust
use near_sdk::{near, env, require, AccountId, PanicOnDefault};
use near_sdk::store::IterableMap;
#[near(contract_state)]
#[derive(PanicOnDefault)]
pub struct Contract {
owner: AccountId,
data: IterableMap<AccountId, String>,
}
#[near]
impl Contract {
#[init]
pub fn new(owner: AccountId) -> Self {
Self {
owner,
data: IterableMap::new(b"d"),
}
}
/// View function - takes &self, free to call
pub fn get_owner(&self) -> &AccountId {
&self.owner
}
/// Change function - takes &mut self, costs gas
pub fn set_data(&mut self, key: AccountId, value: String) {
require!(
env::predecessor_account_id() == self.owner,
"Only owner can set data"
);
self.data.insert(key, value);
}
}
```
**Benefits:**
- `#[near(contract_state)]` handles all serialization automatically
- No need to manually derive `BorshDeserialize`/`BorshSerialize`
- Methods are callable from outside via `#[near]` on impl block
- Initialization validated with `#[init]`
- `PanicOnDefault` prevents uninitialized state access
## Data Structs (Non-Contract)
For data structures used in function arguments/returns:
```rust
/// Use #[near(serializers = [...])] for data structs
#[near(serializers = [json, borsh])]
#[derive(Clone)]
pub struct UserData {
pub name: String,
pub score: u64,
}
```
## Additional Considerations
- Use `#[near(contract_state)]` for the main contract struct
- Use `#[near]` for implementation blocks (replaces second `#[near_bindgen]`)
- Use `#[near(serializers = [json, borsh])]` for data structs returned to users
- Use `#[init]` for initialization methods
- Use `PanicOnDefault` to prevent accidental default initialization
- Mark view functions with `&self` (not `&mut self`)
- Use unique byte prefixes for all collections
## References
- [Smart Contract Structure](https://docs.near.org/smart-contracts/anatomy/)
- [Best Practices](https://docs.near.org/smart-contracts/anatomy/best-practices)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |