Quote from: Ptrck on July 19, 2018, 01:11:31 PM

Quote from: chillcott on July 19, 2018, 12:47:16 PM

Quote from: lesgereron on July 19, 2018, 12:35:12 PM

Quote from: NoG-NoG on July 19, 2018, 11:51:41 AM

Quote from: HappyCaptain on July 19, 2018, 11:37:18 AM

Quote from: CASPER_TEAM on July 19, 2018, 11:00:35 AM

Important information!

Dear friends!

We have to inform you that our ICO is postponed for an indefinite period

Since our company is incorporated in Zug, Switzerland, we have to get the green light from FINMA (The Swiss Financial Market Supervisory Authority) that has not given the necessary approval to conduct the sale on the dates we have planned. We will continue working on resolving this issue so that in the future no legal conflicts can arise.

All the funds contributed by investors will be returned to the wallets you have transferred the money from.

After calculating all the results the tokens will be put in a single spreadsheet and sent to your wallets on the ICO launch day.

As part of the Pre-sale we have attracted fiat investments in exchange for a share in the company so the work on Casper API will be continued, and you can track our progress on github. We will come back to conduct an ICO after gathering the necessary approval and releasing as minimum an alpha version of the product.

We are extremely grateful for your support and we hope that our decision will be taken in the right spirit. Besides, this will allow our potential investors to contribute to a project that already has real world utility.

You still can communicate with team and community here https://t.me/CasperProjectENG , we ll you keep updated.

well I think Casper can resolved this issue more best to be legal process by the way thanks devs for update we looking forward until the end, more power Casper api.

Let us believe that Casper API team can overcome this conflict because we all know the potential of this project. And let's trust the process that they can finish solving this conflict in just a short period of time.

This is really unfortunate for all of us since the project has really lots of potentials to succeed to a very great extent. Though I still believe that the team could make fix this issue and we can all look forward to the success of the project.

Let us all believe that Casper team could fix this small issue since they have already come this far and already showing great result and close to the success of the project. I never doubt the team I know they can make it happen for sure.

Explicitly Casper can surpass this and will have the approval they're waiting. Its not actually a issue but a part of requirements to comply with. Besides, the team and the Casper API seems to be incontestable in any matters especially this one.

This is only just a test trial for the project of Casper Api, same with you I have belief on this project this is just a matter of simple issues

where they can easily resolve it, besides this project became transparent to their community as well since from the start of the project.