This thread is no longer supported - we ask you to join our official telegram chat http://tiny.cc/8zgo5y. |
|
|
|
This thread is no longer supported - we ask you to join our official telegram chat http://tiny.cc/8zgo5y. |
|
|
|
|
KYC/AML and Ethereum address whitelisting registration are required in order to be fully compliant with applicable regulations, and is consistent with security token functionality. It is also required for the following:
- Withdrawing ATLANT Property Tokens to own wallet
- Benefiting from running a node on the ATLANT Network
- Continuing to participate in ATLANT bounty distribution
Please verify your ETH address or stop FUDDING.
Thank you
|
|
|
|
ATLANT Announces Successful Testnet Launch
ATLANT Network Launched in Testnet Ahead of the Upcoming Exchange Launch
Public nodes (testnet):
node-dev1.atlant.io:33780
node-dev2.atlant.io:33780
node-dev3.atlant.io:33780
node-dev4.atlant.io:33780
Sample API requests (JSON-RPC over HTTP):
http://node-dev1.atlant.io:33780/api/v1/stats
http://node-dev2.atlant.io:33780/api/v1/ping
http://node-dev3.atlant.io:33780/api/v1/ethBalance
http://node-dev4.atlant.io:33780/api/v1/kycStatus
Fetch sample property data:
http://node-dev4.atlant.io:33780/api/v1/content/docs/pto/atl123/property/purchase_sale_agreement.pdf
http://node-dev3.atlant.io:33780/api/v1/content/docs/pto/atl123/property/letter_of_intent.pdf
Running a node:
https://github.com/AtlantPlatform/atlant-go
https://github.com/AtlantPlatform/atlant-go/releases/tag/v1.0.0-rc1
ATLANT Node Overview
The ATLANT Node pertains to the functionality of property tokenization and peer-to-peer rentals and is a key part of the Platform’s operations. Being an integral element of the ATLANT distributed system, this component forms a network of nodes, allowing the platform to conduct and maintain information on Property Token Offerings (PTOs) and peer-to-peer (P2P) real estate lease transactions.
Current node implementation (ATLANT-Go) involves operating a distributed store of all information pertaining to PTOs called ADDS (ATLANT Distributed Data Store), which includes property purchase and sale documents necessary for tokenization on a jurisdictional basis such as:
-Title Documents
-Planning Documents
-Sales Contracts
-Commercial Property Standard Enquiries
-Energy Performance Certificates
-Asbestos Reports
-Contamination Reports
-Other Necessary Contracts
Additionally, ADDS implemented within the ATLANT Node stores and catalogs various management company reports on properties, such as:
Tenant Billing and Payments
Property Repairs and Engineering Reports
Property related information such as Insurance, Maintenance, Utilities, etc.
The ATLANT Node is designed from the ground up to interact closely with the Ethereum network, in particular, smart contracts relating to the Platform, PTOs and KYC/AML (Know Your Customer / Anti-Money Laundering identity regulations) for property token holders.
PTO contracts handle PTOs and property token behavior (including KYC/AML checks for token transactions), while the KYC contract is managed by a ServiceRegistry EVM contract, which allows for a fully compliant property token exchange from a regulatory standpoint.
The ATLANT node queries both contract sets in order to fetch secure data. The ATL contract is polled by the node for Platform token holder data, which is then processed by the node to handle proceeds from the Platform’s operations.
Running an ATLANT Node
As per the ATLANT White Paper, both ATL and PTO token holders can derive value from operations conducted on the Platform, provided that two main requirements are met:
1. Being a verified individual (having KYC/AML details completed and registered with the ATLANT Exchange).
2. Running an ATLANT node, which helps to secure the network by distributing property and transactional rental data globally, increasing redundancy.
For a detailed description of ATLANT-Go nodes, and related technology, please review the ATLANT white paper, beginning on page 33.
ATLANT-Go is tightly coupled with the ATLANT Exchange, for the sake of compliance (KYC/AML service), inexpensive data storage and redundancy (ADDS) and value distribution (based on work performed).
The ATLANT team is working hard on finalizing the integration of these major Platform components, and we look forward to releasing and integrating the remaining components quickly.
The ATLANT Node is open-source software and has its source code published on the official ATLANT GitHub: https://github.com/AtlantPlatform
The source code is available for review:
ATLANT Node
https://github.com/AtlantPlatform/atlant-go
ATLANT PTO contracts
https://github.com/AtlantPlatform/atlant-pto-contracts
Modified IPFS node (utilized by ATLANT-Go)
https://github.com/AtlantPlatform/go-ipfs
Current node release is available at
https://github.com/AtlantPlatform/atlant-go/releases/tag/v1.0.0-rc1
|
|
|
|
We are continuing our series of posts, recapping our achievements of 2018:ATLANT’s Proposed Base Security Token Standard (ERC-1462) Accepted as Draft by Ethereum Contributors
Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. The draft has been reviewed and merged into the EIP registry, and is now publicly available for community review at EIPS section of the Ethereum.org website.
ATLANT’s Motivation
There are several security token standards which have been proposed recently, however ATLANT team has concerns about most of these proposals. In our view issues stem mainly from the scope of each of the EIPs, which contain many project or market-specific details. Since many EIPs were designed and backed by for-profit companies, they capture niche requirements which are excessive for general use cases. Further explanations and rationale with examples and case studies are available in the original draft of the ERC-1462 standard.
ATLANT proposes an EIP which is simple, yet modular solution to creating base security tokens for the widest possible scope of applications. ERC-1462 is designed so that it may be used by issuers out of the box, or be built and improved upon. Other issuers are able to add further restrictions and policies to their tokens, using proposed functions and implementation, yet their creativity will not be limited in any way, while using ERC-1462.
We believe that a pragmatic approach is necessary to create a clear and concise general security token specification. Due to this approach, ATLANT’s proposed ERC-1462 draft has now become the first merged standard draft addressing the general case of Security Token utilization on the Ethereum blockchain. We continue collecting feedback from the community, as well as developing our own projects which leverage ERC-1462.
For further details, please visit the EIP-1462 page for ATLANT’s proposed security token standard in the EIPS section of the Ethereum.org website.
|
|
|
|
We are continuing our series of posts, recapping our achievements of 2018:ATLANT’s Proposed Base Security Token Standard (ERC-1462) Accepted as Draft by Ethereum Contributors
Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards. The draft has been reviewed and merged into the EIP registry, and is now publicly available for community review at EIPS section of the Ethereum.org website.
ATLANT’s Motivation
There are several security token standards which have been proposed recently, however ATLANT team has concerns about most of these proposals. In our view issues stem mainly from the scope of each of the EIPs, which contain many project or market-specific details. Since many EIPs were designed and backed by for-profit companies, they capture niche requirements which are excessive for general use cases. Further explanations and rationale with examples and case studies are available in the original draft of the ERC-1462 standard.
ATLANT proposes an EIP which is simple, yet modular solution to creating base security tokens for the widest possible scope of applications. ERC-1462 is designed so that it may be used by issuers out of the box, or be built and improved upon. Other issuers are able to add further restrictions and policies to their tokens, using proposed functions and implementation, yet their creativity will not be limited in any way, while using ERC-1462.
We believe that a pragmatic approach is necessary to create a clear and concise general security token specification. Due to this approach, ATLANT’s proposed ERC-1462 draft has now become the first merged standard draft addressing the general case of Security Token utilization on the Ethereum blockchain. We continue collecting feedback from the community, as well as developing our own projects which leverage ERC-1462.
For further details, please visit the EIP-1462 page for ATLANT’s proposed security token standard in the EIPS section of the Ethereum.org website.
|
|
|
|
ATLANT Releases Ethereum Playbook
A simple alternative to the Truffle Framework 
Inspired by Ansible Playbooks, ATLANT’s Ethereum Playbook is a declarative tool for comprehensive DApp automation, while remaining as minimalistic as possible. As a part of the ATLANT team’s open-source effort to make Ethereum development easier, Ethereum Playbook is the first step towards simple yet flexible and powerful DApp management.
Released as a command-line application, this tool is intended for ease of use and does not have a steep learning curve.
Ethereum Playbook greatly simplifies working with Ethereum DApps, allowing for seamless configuration and deployment of numerous DApps without losing control over the decentralized infrastructure.
The Playbook uses a simple and clean YAML syntax for creating static specifications. The flexibility of declarative configuration brings confidence into your decentralized application development lifecycle irrespective of the size of target deployment: single DApp or multiple DApp infrastructures.
Ethereum Playbook is not an integral part of the ATLANT platform, rather, it is used to facilitate DApp management within the platform as an internal product. We have decided to release the first public version of the Ethereum Playbook in an attempt to spark further development, laying foundation for a new community-driven project targeting Ethereum developers worldwide.
Download Ethereum Playbook:
https://github.com/AtlantPlatform/ethereum-playbook/releases/latest
Release builds available for Windows, OS X and Linux.
Source code is available on GitHub:
https://github.com/AtlantPlatform/ethereum-playbook
|
|
|
|
ATLANT Releases Ethereum Playbook
A simple alternative to the Truffle Framework
Inspired by Ansible Playbooks, ATLANT’s Ethereum Playbook is a declarative tool for comprehensive DApp automation, while remaining as minimalistic as possible. As a part of the ATLANT team’s open-source effort to make Ethereum development easier, Ethereum Playbook is the first step towards simple yet flexible and powerful DApp management.
Released as a command-line application, this tool is intended for ease of use and does not have a steep learning curve.
Ethereum Playbook greatly simplifies working with Ethereum DApps, allowing for seamless configuration and deployment of numerous DApps without losing control over the decentralized infrastructure.
The Playbook uses a simple and clean YAML syntax for creating static specifications. The flexibility of declarative configuration brings confidence into your decentralized application development lifecycle irrespective of the size of target deployment: single DApp or multiple DApp infrastructures.
Ethereum Playbook is not an integral part of the ATLANT platform, rather, it is used to facilitate DApp management within the platform as an internal product. We have decided to release the first public version of the Ethereum Playbook in an attempt to spark further development, laying foundation for a new community-driven project targeting Ethereum developers worldwide.
Download Ethereum Playbook:
https://github.com/AtlantPlatform/ethereum-playbook/releases/latest
Release builds available for Windows, OS X and Linux.
Source code is available on GitHub:
https://github.com/AtlantPlatform/ethereum-playbook
|
|
|
|
ATLANT Announces Partnership with BitCratic ATL tokens are now fully supported by BitCraticThe ATLANT token (ATL) is now fully supported by BitCratic, a semi decentralized exchange with off-chain order book and on-chain settlements.ABOUT ATLANT
ATLANT is a revolutionary global real estate platform enabling tokenization of real estate ownership and P2P rentals. The rapidly growing ATLANT team is both distributed and global. For additional details please visit https://atlant.io
ABOUT BITCRATIC
BitCratic is a semi-decentralized exchange. Majority of the operations are handled via the blockchain which allows traders to retain custody of their tokens. BitCratic uses off-chain order book with on-chain settlements. Currently BitCratic uses Etherdelta smart contracts and order book. For more info please visit www.bitcratic.com |
|
|
|
ATLANT Announces Partnership with BitCratic ATL tokens are now fully supported by BitCraticThe ATLANT token (ATL) is now fully supported by BitCratic, a semi decentralized exchange with off-chain order book and on-chain settlements.ABOUT ATLANT
ATLANT is a revolutionary global real estate platform enabling tokenization of real estate ownership and P2P rentals. The rapidly growing ATLANT team is both distributed and global. For additional details please visit https://atlant.io
ABOUT BITCRATIC
BitCratic is a semi-decentralized exchange. Majority of the operations are handled via the blockchain which allows traders to retain custody of their tokens. BitCratic uses off-chain order book with on-chain settlements. Currently BitCratic uses Etherdelta smart contracts and order book. For more info please visit www.bitcratic.com |
|
|
|
ATLANT Announces Partnership with BitCratic ATL tokens are now fully supported by BitCraticThe ATLANT token (ATL) is now fully supported by BitCratic, a semi decentralized exchange with off-chain order book and on-chain settlements.ABOUT ATLANT
ATLANT is a revolutionary global real estate platform enabling tokenization of real estate ownership and P2P rentals. The rapidly growing ATLANT team is both distributed and global. For additional details please visit https://atlant.io
ABOUT BITCRATIC
BitCratic is a semi-decentralized exchange. Majority of the operations are handled via the blockchain which allows traders to retain custody of their tokens. BitCratic uses off-chain order book with on-chain settlements. Currently BitCratic uses Etherdelta smart contracts and order book. For more info please visit www.bitcratic.com |
|
|
|
How does decentralized KYC work on ATLANT? 
As previously stated, both procedures are required in order to be fully compliant with applicable rules and regulations in most jurisdictions where we plan to operate.
ATLANT strives to be as compliant and transparent as possible, and given that we have ongoing processes to acquire necessary licensing for operation, it is crucial for us to follow the rules enacted by regulators and relevant government and regional authorities.
ATLANT KYC Procedures
Token withdrawals and/or payouts on ATLANT require users to pass a number of standard AML/KYC procedures, including list screenings (SDN, PEPs, etc), due diligence and document checks. Most of these checks are performed automatically after submission of KYC documents on the ATLANT Platform. Others, however, require a manual effort by internal compliance officers, or further interaction with users.
We recognize that this is sometimes an arduous process, and to alleviate this inconvenience, we are in a process of integrating 3rd party KYC providers, among them, a regulated US Trust, to expedite verification procedures.
Another difficulty which we are addressing with our legal team is the volatility of governments’ positions in various countries with respect to security tokens and cryptocurrencies, and proliferation of existing and newly enacted laws and regulations.
Further, we are working on more integrations in our KYC process, including well known players such as Civic and Telegram Passport — these are expected to eventually streamline KYC user experience, as we look to make the process easier for clients.
Described KYC/AML procedures are centralized as in most traditional financial institutions, predominantly for GDPR compliance and other regulatory requirements. Whitelisting, however, involves storing whitelisted addresses on the blockchain.
ATLANT AW Procedures
Address Whitelisting is a KYC-related concept which is inherent to ATLANT and its proposed model of operations.
Any event involving token transfers to external Ethereum addresses would require a user to whitelist these addresses, provided that KYC/AML procedures have been passed successfully. At this stage, an Ethereum-based ledger representing a decentralized KYC registry comes into play.
The current implementation of ATLANT KYC Registry brings transparency by enabling any application, both internal to ATLANT or external (e.g. regulators), to check a particular address, verifying its KYC status near-instantly without suffering from possible service downtime/unavailability or tampered records.
Once Ethereum address is entered on the ATLANT Platform (Verification page), we automatically check the address for relevant transactions between it and ATLANT, when ‘Verify’ is clicked. In case there’s one or more transactions, the platform deducts a whitelisting fee and adds the address to the Ethereum ledger, marking it as verified by ATLANT.
Whitelisting involves paying a small verification fee which includes a network fee and imbeds costs for compliance and integration/monitoring. Please note — we are trying to streamline the KYC procedures (per above), and hope to further automate and lower the costs involved.
You can always check your address status on ATLANT via any Ethereum explorer, (e.g. Etherscan):
1. Navigate to
https://etherscan.io/address/0xd63a77fe246c4a0095796b13c33c15e55fea1f6c#readContract
2. Insert your external (personal) address into the “address” textbox (“getStatus” panel) and click “Query”
3. Check the number returned by Etherscan. “1” stands for “verified by ATLANT”.
Statuses will be more nuanced in the future but some tentative guidelines are:
“0” — non-verified address
“1” — verified address
“2” — suspended address
Sample values:
Verified: 0x65dc3935b20eAaa9aAb0d8AcCfAC99f3cF862823
Non-verified: 0xA10Da3724c7A7b8Ad2E6Aa8a439f9AC38a9a3182
Additionally, we have implemented a versatile approach in AW, making it possible for external KYC providers to conduct whitelisting on behalf of ATLANT. This is useful for situations when multiple apps or external providers need to be allowed, to conduct AW. External KYC provider address may be assigned or revoked at any time by ATLANT.
We encourage everyone to verify KYC contract source code:
https://etherscan.io/address/0xd63a77fe246c4a0095796b13c33c15e55fea1f6c#code
In case you require further help with getting verified on ATLANT, or have other issues, please feel free to contact support by writing to help@atlant.io or submitting a ticket on the ATLANT Helpdesk Portal https://helpdesk.atlant.io. Please make sure to use the same email address as you used to register on ATLANT, when submitting tickets.
|
|
|
|
I was away, just got back home, happy to have ended the KYC Procedures and the Address Whitelisting Procedures. All my support to the team. Go Atlant, Summer holidays coming  Thank you for your support. |
|
|
|
How does decentralized KYC work on ATLANT?
As previously stated, both procedures are required in order to be fully compliant with applicable rules and regulations in most jurisdictions where we plan to operate.
ATLANT strives to be as compliant and transparent as possible, and given that we have ongoing processes to acquire necessary licensing for operation, it is crucial for us to follow the rules enacted by regulators and relevant government and regional authorities.
ATLANT KYC Procedures
Token withdrawals and/or payouts on ATLANT require users to pass a number of standard AML/KYC procedures, including list screenings (SDN, PEPs, etc), due diligence and document checks. Most of these checks are performed automatically after submission of KYC documents on the ATLANT Platform. Others, however, require a manual effort by internal compliance officers, or further interaction with users.
We recognize that this is sometimes an arduous process, and to alleviate this inconvenience, we are in a process of integrating 3rd party KYC providers, among them, a regulated US Trust, to expedite verification procedures.
Another difficulty which we are addressing with our legal team is the volatility of governments’ positions in various countries with respect to security tokens and cryptocurrencies, and proliferation of existing and newly enacted laws and regulations.
Further, we are working on more integrations in our KYC process, including well known players such as Civic and Telegram Passport — these are expected to eventually streamline KYC user experience, as we look to make the process easier for clients.
Described KYC/AML procedures are centralized as in most traditional financial institutions, predominantly for GDPR compliance and other regulatory requirements. Whitelisting, however, involves storing whitelisted addresses on the blockchain.
ATLANT AW Procedures
Address Whitelisting is a KYC-related concept which is inherent to ATLANT and its proposed model of operations.
Any event involving token transfers to external Ethereum addresses would require a user to whitelist these addresses, provided that KYC/AML procedures have been passed successfully. At this stage, an Ethereum-based ledger representing a decentralized KYC registry comes into play.
The current implementation of ATLANT KYC Registry brings transparency by enabling any application, both internal to ATLANT or external (e.g. regulators), to check a particular address, verifying its KYC status near-instantly without suffering from possible service downtime/unavailability or tampered records.
Once Ethereum address is entered on the ATLANT Platform (Verification page), we automatically check the address for relevant transactions between it and ATLANT, when ‘Verify’ is clicked. In case there’s one or more transactions, the platform deducts a whitelisting fee and adds the address to the Ethereum ledger, marking it as verified by ATLANT.
Whitelisting involves paying a small verification fee which includes a network fee and imbeds costs for compliance and integration/monitoring. Please note — we are trying to streamline the KYC procedures (per above), and hope to further automate and lower the costs involved.
You can always check your address status on ATLANT via any Ethereum explorer, (e.g. Etherscan):
1. Navigate to
https://etherscan.io/address/0xd63a77fe246c4a0095796b13c33c15e55fea1f6c#readContract
2. Insert your external (personal) address into the “address” textbox (“getStatus” panel) and click “Query”
3. Check the number returned by Etherscan. “1” stands for “verified by ATLANT”.
Statuses will be more nuanced in the future but some tentative guidelines are:
“0” — non-verified address
“1” — verified address
“2” — suspended address
Sample values:
Verified: 0x65dc3935b20eAaa9aAb0d8AcCfAC99f3cF862823
Non-verified: 0xA10Da3724c7A7b8Ad2E6Aa8a439f9AC38a9a3182
Additionally, we have implemented a versatile approach in AW, making it possible for external KYC providers to conduct whitelisting on behalf of ATLANT. This is useful for situations when multiple apps or external providers need to be allowed, to conduct AW. External KYC provider address may be assigned or revoked at any time by ATLANT.
We encourage everyone to verify KYC contract source code:
https://etherscan.io/address/0xd63a77fe246c4a0095796b13c33c15e55fea1f6c#code
In case you require further help with getting verified on ATLANT, or have other issues, please feel free to contact support by writing to help@atlant.io or submitting a ticket on the ATLANT Helpdesk Portal https://helpdesk.atlant.io. Please make sure to use the same email address as you used to register on ATLANT, when submitting tickets.
|
|
|
|
How does decentralized KYC work on ATLANT?
As previously stated, both procedures are required in order to be fully compliant with applicable rules and regulations in most jurisdictions where we plan to operate.
ATLANT strives to be as compliant and transparent as possible, and given that we have ongoing processes to acquire necessary licensing for operation, it is crucial for us to follow the rules enacted by regulators and relevant government and regional authorities.
ATLANT KYC Procedures
Token withdrawals and/or payouts on ATLANT require users to pass a number of standard AML/KYC procedures, including list screenings (SDN, PEPs, etc), due diligence and document checks. Most of these checks are performed automatically after submission of KYC documents on the ATLANT Platform. Others, however, require a manual effort by internal compliance officers, or further interaction with users.
We recognize that this is sometimes an arduous process, and to alleviate this inconvenience, we are in a process of integrating 3rd party KYC providers, among them, a regulated US Trust, to expedite verification procedures.
Another difficulty which we are addressing with our legal team is the volatility of governments’ positions in various countries with respect to security tokens and cryptocurrencies, and proliferation of existing and newly enacted laws and regulations.
Further, we are working on more integrations in our KYC process, including well known players such as Civic and Telegram Passport — these are expected to eventually streamline KYC user experience, as we look to make the process easier for clients.
Described KYC/AML procedures are centralized as in most traditional financial institutions, predominantly for GDPR compliance and other regulatory requirements. Whitelisting, however, involves storing whitelisted addresses on the blockchain.
ATLANT AW Procedures
Address Whitelisting is a KYC-related concept which is inherent to ATLANT and its proposed model of operations.
Any event involving token transfers to external Ethereum addresses would require a user to whitelist these addresses, provided that KYC/AML procedures have been passed successfully. At this stage, an Ethereum-based ledger representing a decentralized KYC registry comes into play.
The current implementation of ATLANT KYC Registry brings transparency by enabling any application, both internal to ATLANT or external (e.g. regulators), to check a particular address, verifying its KYC status near-instantly without suffering from possible service downtime/unavailability or tampered records.
Once Ethereum address is entered on the ATLANT Platform (Verification page), we automatically check the address for relevant transactions between it and ATLANT, when ‘Verify’ is clicked. In case there’s one or more transactions, the platform deducts a whitelisting fee and adds the address to the Ethereum ledger, marking it as verified by ATLANT.
Whitelisting involves paying a small verification fee which includes a network fee and imbeds costs for compliance and integration/monitoring. Please note — we are trying to streamline the KYC procedures (per above), and hope to further automate and lower the costs involved.
You can always check your address status on ATLANT via any Ethereum explorer, (e.g. Etherscan):
1. Navigate to
https://etherscan.io/address/0xd63a77fe246c4a0095796b13c33c15e55fea1f6c#readContract
2. Insert your external (personal) address into the “address” textbox (“getStatus” panel) and click “Query”
3. Check the number returned by Etherscan. “1” stands for “verified by ATLANT”.
Statuses will be more nuanced in the future but some tentative guidelines are:
“0” — non-verified address
“1” — verified address
“2” — suspended address
Sample values:
Verified: 0x65dc3935b20eAaa9aAb0d8AcCfAC99f3cF862823
Non-verified: 0xA10Da3724c7A7b8Ad2E6Aa8a439f9AC38a9a3182
Additionally, we have implemented a versatile approach in AW, making it possible for external KYC providers to conduct whitelisting on behalf of ATLANT. This is useful for situations when multiple apps or external providers need to be allowed, to conduct AW. External KYC provider address may be assigned or revoked at any time by ATLANT.
We encourage everyone to verify KYC contract source code:
https://etherscan.io/address/0xd63a77fe246c4a0095796b13c33c15e55fea1f6c#code
In case you require further help with getting verified on ATLANT, or have other issues, please feel free to contact support by writing to help@atlant.io or submitting a ticket on the ATLANT Helpdesk Portal https://helpdesk.atlant.io. Please make sure to use the same email address as you used to register on ATLANT, when submitting tickets.
|
|
|
|
KYC Procedures and ATLANT Address Whitelisting Procedures done and happy with it. I was away, got back right on time. All my support to Atlant team. => https://trade.atlant.io Thank you for your support Jcga. |
|
|
|
Ukraine2020, Per our terms and conditions, we do not accept non-English documents. The only exceptions are in situations where our compliance officers have specific knowledge of the languages and documents submitted, and further clarification. Currently the world has 37 million native Ukrainian speakers which is approximately 0.4% of the 7.7 billion world's population. Thus unfortunately, at present, for business and other reasons, ATLANT is unable to justify a compliance officer who is versed in the Ukrainian language, and ask you to provide documents in English. We investigated your claim that “in Ukraine there are no passports or IDs in English”, and it is false. We advise you to study the legislation of Ukraine, or read these articles in Wikipedia: https://en.wikipedia.org/wiki/Ukrainian_passporthttps://en.wikipedia.org/wiki/Ukrainian_identity_cardWe would like to ask you to kindly stop your ongoing FUD, and provide necessary documents for verification, if you are interested in undergoing KYC/AML on ATLANT. Regards, ATLANT Team
|
|
|
|
Dashboard Retirement Users had an opportunity to withdraw ATL from the dashboard, ico.atlant.io for over a year. As we draw closer to the ATLANT Platform launch, we will be retiring the ico.atlant.io dashboard.
ATL Token Withdrawal
ATLANT team is encouraging everyone to make free withdrawals from their dashboard until 12/31/18 into personal Ethereum addresses. ATL is an ERC-20 token and is compatible with most Ethereum wallets, though we recommend Atlant Android Wallet, Coinomi or MEW for ease of use.
In a gradual phaseout, starting 1/1/19, quantity of ATL equivalent to 3% of each custodied balance observed on 1/1/19, will be deducted from each account daily, as a custody fee. When all dashboard balances reach zero, the dashboard will be retired.
For further help look at instructions on how to withdraw ATL: https://blog.atlant.io/faq-how-to-withdraw-atl-tokens-b9879c56d568 or write to help@atlant.io. |
|
|
|
|
Show Posts
