Using contract tools package to create FT #2853
Open
+122
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
garikbesson
changed the title
bucanero
temporarily deployed
to
ft-contract-tools-tutorial - docs.near.org PR #2853
Render
Destroyed
garikbesson
changed the title
bucanero
reviewed
Nov 10, 2025
Comment on lines
+19
to
+22
| - NEP-141 (fungible token), extension NEP-148. | ||
| - NEP-145 (storage management), and integrations for the fungible token and non-fungible token standards. | ||
| - NEP-171 (non-fungible token), extensions NEP-177, NEP-178, NEP-181. | ||
| - NEP-297 (events). |
Collaborator
There was a problem hiding this comment.
I think we should add links to the NEPs for better cross-reference.
Suggested change
| - NEP-141 (fungible token), extension NEP-148. | |
| - NEP-145 (storage management), and integrations for the fungible token and non-fungible token standards. | |
| - NEP-171 (non-fungible token), extensions NEP-177, NEP-178, NEP-181. | |
| - NEP-297 (events). | |
| - [NEP-141](https://github.com/near/NEPs/blob/master/neps/nep-0141.md) (fungible token), extension NEP-148. | |
| - NEP-145 (storage management), and integrations for the fungible token and non-fungible token standards. | |
| - NEP-171 (non-fungible token), extensions NEP-177, NEP-178, NEP-181. | |
| - NEP-297 (events). |
bucanero
reviewed
Nov 10, 2025
|
|
||
| The difference of this example from the [FT contract](https://github.com/near-examples/FT) based on `near_contract_standards` package is the approach of using deriving macros to implement NEP standards and common patterns. | ||
|
|
||
| When we use deriving macros, we can bring `near_contract_standards` implementations into our contract without writing boilerplate code for the each method. That allows us to focus on the unique logic of our contract like minting/burning logic, access control, other custom features. So, this collection of common tools and patterns (mostly in the form of derive macros) is as a sort of OpenZeppelin for NEAR. |
Collaborator
There was a problem hiding this comment.
Suggested change
| When we use deriving macros, we can bring `near_contract_standards` implementations into our contract without writing boilerplate code for the each method. That allows us to focus on the unique logic of our contract like minting/burning logic, access control, other custom features. So, this collection of common tools and patterns (mostly in the form of derive macros) is as a sort of OpenZeppelin for NEAR. | |
| When we use deriving macros, we can bring `near_contract_standards` implementations into our contract without writing boilerplate code for each method. That allows us to focus on the unique logic of our contract like minting/burning logic, access control, other custom features. So, this collection of common tools and patterns (mostly in the form of derive macros) is as a sort of OpenZeppelin for NEAR. |
bucanero
reviewed
Nov 10, 2025
| - `storage_unregister` | ||
| - `storage_withdraw` | ||
|
|
||
| To bring basic owner methods to our contract, we derived also `Owner` macro which adds the following methods: |
Collaborator
There was a problem hiding this comment.
Suggested change
| To bring basic owner methods to our contract, we derived also `Owner` macro which adds the following methods: | |
| To bring basic owner methods to our contract, we also derived the `Owner` macro which adds the following methods: |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.