KYC Guidelines / Major Partners

Hey Everyone,

  • Here is the link to the 50% off discounted course on Crypto Taxation from the SEC, IRS, and CRA:
  • It covers some of the most recent information updates from the Government of Canada and the Securities Exchange Commission (SEC) and Internal Revenue Service (IRS) regarding taxation policies and how crypto is classified as a property, or asset depending on it’s use, as well as Bitcoin legality by country.
  • I wrote this course for CPD Formula and am offering my readers an exclusive 50% discount on the course.
  • The course has 6 -10 minute video sections that cover the following topics:

Section 1. Canada Revenue Agency and Virtual Currency Compliance

Section 2. Japan, UK, USA, Canada Bitcoin Legal Tender Status

Section 3. Review of Securities and Exchange Commission in the USA

Section 4. Central Bank Issued Currencies (Digital Yuan, Petro)

Section 5. IRS View on Cryptocurrency

This course is good for anyone who invests in Crypto, and answers the most common taxation questions in Canada and the USA. Please share freely!

An overview of banking and security laws in the virtual currency industry. Review of countries, governing agencies, and regulating bodies.

Topics Include:
Canada Revenue Agency and Canadian Virtual Currency Regulations
Review of Securities and Exchange Commission in the USA
Central Bank Issued Currencies (Digital Yuan, Petro)
IRS View on Cryptocurrency

Know Your Customer Policy:  Teen Coin is working to know it’s members, patrons, clients, and customers across multiple levels of interaction including one on one, through the use of social media, and with blanket publishing.

Record Keeping Procedures are enabled through ongoing and evolutionary development of project specifics, focusing on clarity and relevancy to the organization and it’s goals. Without a centralized governing body, record keeping is maintained publicly on the decentralized model where ownership is measured by percentage of ownership in the Teen Coin supply.

To date, large cash transactions can be arranged with so it can be accurately documented for business purposes. We have created a transparent and clear platform for trading coins on the Saturn Exchange and Finexbox, with attention to long term financing and respecting the anonymity of development of projects by third parties and decentralized organizations as part of a global engagement strategy.

Our electronic funds transfer policy coincides with the interactions involved with public buying and selling at market prices on Saturn Exchange and Finexbox, our two exchange listings. One is a decentralized exchange, and the other is centralized. Owners of coins can trade on the exchange of their choice.

Our primary goal is to find a financing partner who will take a major investment share in the project, so that we are able to sell some of our coin reserves to finance business activities. Negotiations are ongoing with potential partners throughout the course of the development of the Teen project to be first to market and reward our coin holders.

Coin transactions are almost always financial in nature, and are conducted on publicly traded and respectable platforms, and TEEN is also compatible with the ETH Mobile Wallets Imtoken, the MyEthereum Wallet, and the SATURN Wallet, and other major ETH Wallets.

Financials in Canadian Dollars:

2018 Year End:  Raised $4500 by selling 600,000,000 Teen Coins at 0.0000075. Funds Used to pay for Air Coins Game Development and Listing. Total coins in reserve 12.9 Billion Coins estimated value using IPO price of 0.0000075 making the valuation of Teen Coin worth $96,750.

2019 Year End: No sales were done in 2019 and reserves remained at 12.9 Billion. The 600,000,000 coins on the market traded between .00000075 and .000175 per coin.

2020 Reporting expected March, 2021.

Major investors can email for current reporting.

Other investors can buy, sell, trade freely at Saturn Exchange or Finexbox.


Teen Coin has enabled risk planning throughout it’s strategic policy making and organizational development. Maintaining a stringent bones policy for managing risk has been distributed between a skeleton of credit risk, market risk, liquidity risk, model risk, and operational risk.

Under the analysis, a variety of risk points are identified so that shareholders and investors, and our loyalty users, are protected as best as possible in our validation frameworks, risk measurement and reporting systems.


Our policy continues to guide our monitoring and reporting to ensure compliance with the SEC, CRA, CDS, and CCDC, as the project aspires to join the markets as an OTC security. More communication and corporate governance needs to be conducted to meet the CCDC requirements for Teen Coin to be publicly traded on the TMX, but does not mean it could not be traded in the future.

Since CDS and CCDC were recognized in 2012 by the Bank of Canada as being important, it is also important to Teen Coin to recognize the importance of having transparent and public policy that best represents the democratic interests of shareholders and regulators alike.

As Teen Coin is an inventor of intellectual property in the Fintech Sector, there is no doubt that the testing of new financial tools, systems, reporting mechanisms, health, and security will continue to evolve and adapt in unregulated territory, and that business done in these areas are done in good faith.

As such, Teen Coin will continue to develop and maintain metrics on risk levels and prepare analyses summarizing results, as well as document procedures for financial risk processes, and use operational results to guide future organizational and strategic reporting.

Google Health and Teen Coin Using Google Cloud

Teen Coin has enabled a series of backbone security services to further mitigate risk within the cloud by adding the role of the Crytocurrency Wallet Manager to the IAM and Google Admin profiles, servicing Teen Coin as innovator in new security policy development and administration.


Customer Impact
RollbackEvent Model Factors
Deployment Speed
All-at-onceAll at onceRedeploy older versionAny event model at low concurrency rateImmediate
Blue/GreenAll at once with some level of production environment testing beforehandRevert traffic to previous environmentBetter for async and sync event models at medium concurrency workloadsMinutes to hours of validation and then immediate to customers
Canary/Linear1–10% typical initial traffic shift, then phased increases or all at onceRevert 100% of traffic to previous deploymentBetter for high concurrency workloadsMinutes to hours

A best practice for deployments in a microservice architecture is to ensure that a change does not break the service contract of the consumer. If the API owner makes a change that breaks the service contract and the consumer is not prepared for it, failures can occur.

To understand the impact of deployment changes, you need to know which consumers are using your API. You can collect metadata on usage by using API keys, and these can also act as a form of contract if a breaking change is made to an API.

When customers want to soften the impact of breaking changes to an API, they can clone the API and route customers to a different subdomain (for example, to ensure that existing consumers aren’t impacted. This approach allows customers to only deploy new changes to the new API service contract, but comes with trade-offs. Customers taking this approach need to maintain two versions of the API, and will deal with infrastructure management and provisioning overhead.


Canary deployments are an ever-increasing way for you to leverage the new release of a software in a controlled environment and enabling rapid deployment cycles. Canary deployments involve deploying a small number of requests to the new change to analyze impact to a small number of your users.

With canary deployments in API Gateway, you can deploy a change to your backend endpoint (for example, Lambda) while still maintaining the same API Gateway HTTP endpoint for consumers. In addition, you can also control what percentage of traffic is routed to new deployment and for a controlled traffic cut-over. A practical scenario for a canary deployment might be a new website. You can monitor the click-through rates on a small number of end users before shifting all traffic to the new deployment.
Implementing canary deployments of AWS Lambda functions with alias traffic shifting

Learn how to implement canary deployments of AWS Lambda functions.

What is an Embedded Analytics Developer?

Embedded Analytics Developers integrate interactive dashboards and analytics capabilities directly within software-as-a-service (SaaS) applications. Developers building SaaS applications can now offer embedded, pre-configured (canned) dashboards to all end-users, while also providing sophisticated ad-hoc data exploration and dashboard-building (authoring) capabilities to power users. \


Myteencoin has conducted due diligence activities on 3rd party cryptographic vendors to satisfy “the security requirements that will be satisfied by a cryptographic module, providing four increasing, qualitative levels intended to cover a wide range of potential applications and environments. The areas covered, related to the secure design and implementation of a cryptographic module, include specification; ports and interfaces; roles, services, and authentication; finite state model; physical security; operational environment; cryptographic key management; electromagnetic interference/electromagnetic compatibility (EMI/EMC); self-tests; design assurance; and mitigation of other attacks.”

In 24 months (Sept. 2018-20), Teen Coin has achieved a net zero downtime rate because of it’s excellent design and rigorous testing. Over 100 platforms were tested during the beta phase of deployment, and it was deemed that Imtoken and Finexbox are most secure and scalable, while also eliminating liability on Teen. Sourcing the services from scalable partners has proven to be highly successful.