CIP: 4
Title: Subassets
Author: Jeremy Johnson (J-Dog)
Status: Draft
Type: Standards
Created: 2016-01-29
This file contains 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
Verifying that +jdog is my blockchain ID. https://onename.com/jdog |
I hereby claim:
- I am jdogresorg on github.
- I am jdog (https://keybase.io/jdog) on keybase.
- I have a public key ASCqA9Nj5cvataw5E2I0Hfnz08_KKKuFa-vfIDmvnlryBQo
To claim this, I am signing this object:
CIP: 12 Title: Memo Requirement through Broadcasts Authors: Jeremy Johnson Discussions-To: https://counterpartytalk.org/t/memo-requirement-through-broadcasts/3147 Status: Draft Type: Standards Created: 2017-06-07
Counterparty, an innovative platform for peer-to-peer markets and financial instruments, is looking for a dynamic Community Outreach Manager(s) to work with the Counterparty Foundation and community to drive engagement, inform and support the community, and help grow awareness of the Counterparty platform.
-
Spend 6-8 hours each week working on community outreach
-
Community Newsletter once a month
This file contains 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
{ | |
"asset": "MYTOKEN", | |
"description": "This is a text description of MYTOKEN", | |
"image": "http://www.mysite.com/mytoken.png", | |
"website": "http://www.mysite.com", | |
"pgpsig": "http://www.mysite.com/MYTOKEN.pgp", | |
"name": "Token Name", | |
"owner": { |
This file contains 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
{ | |
"title": "Enhanced Asset Information Specification Schema", | |
"type": "object", | |
"$schema": "http://json-schema.org/draft-04/schema", | |
"version": "2.0.0", | |
"properties": { | |
"asset": { | |
"type": "string", | |
"description": "The asset name that represents the token" |
CIP: 25 Title: Enhanced Asset Information Specification Author: Jeremy Johnson Discussions-To: https://counterpartytalk.org/t/enhanced-asset-information-specification/6431 Status: Draft Type: Process Created: 2022-09-13
This file contains 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
# Counterparty Thoughts / Features | |
- AML / KYC Compliant tokens | |
- Have heard consistent feedback over the years that companies/projects dont issue on CP cuz they can't do so and be in AML/KYC compliance. | |
- We need to provide a way for Companies can do their own AML/KYC (external), and then maintain lists of addresses on CP | |
- From a functionality perspective we just need : | |
- ability to create/edit LIST of addresses (whitelists/blacklists) | |
- update issuances to indicate new token type (AML/KYC compliant) and reference to LIST | |
- Update Send / Order / Dispenser logic to support AML/KYC tokens using LIST | |