Categories
- 17.3K All Categories
- 9.5K Mining
- 574 Pool Discussion
- 378 Promotional
- 1.4K General Project Discussion (non-technical)
- 485 Education
- 811 Protocol and Client discussion
- 170 web3-js
- 29 Whisper
- 16 Swarm
- 3 RLP
- 303 IoT & Hardware
- 1.2K Smart Contracts and Dapps
- 28 Serpent
- 359 Solidity
- 664 Projects
- 1.2K Reference clients code and builds
- 249 Eth & AlethZero- Cpp Implementation
- 471 Geth - Go Implementation
- 242 Mist
- 15 Node.js Implementation
- 36 Python Implementation
- 49 Mix
- 36 Other Implementations
- 170 Meetups
- 40 Other Events
- 226 Jobs & Skills
- 281 Press and Articles
- 75 Audio/Video
- 296 Ether Sale
- 1.2K Other Languages
- 96 Chinese
- 255 German
- 33 Italian
- 111 French
- 3 Hebrew
- 42 Japanese
- 75 Portugese
- 46 Romanian
- 185 Russian
- 231 Spanish
- 47 Turkish
- 125 Watercooler
Tokens / Managing Unique Characteristics
broadk
Member Posts: 1 ✭
Hi,
New to smart contracts so I'm hoping someone can offer an architectural perspective. I'd like to create a new class of token which could be linked to a physical item. As such there will be a limited number of tokens which map to a batch of items. Each item in the batch would be uniquely numbered IRL, e.g. 1 of 10. It's unclear to me whether it is feasible to uniquely describe each token (and give it a unique price) within a single contract or would I be better creating a unique contract for each? Clearly I would prefer the former given their intrinsic physical relationship.
Is there any best practice for this type of use-case?
kind regards
k.
New to smart contracts so I'm hoping someone can offer an architectural perspective. I'd like to create a new class of token which could be linked to a physical item. As such there will be a limited number of tokens which map to a batch of items. Each item in the batch would be uniquely numbered IRL, e.g. 1 of 10. It's unclear to me whether it is feasible to uniquely describe each token (and give it a unique price) within a single contract or would I be better creating a unique contract for each? Clearly I would prefer the former given their intrinsic physical relationship.
Is there any best practice for this type of use-case?
kind regards
k.
Comments