As a community-driven project, we highly value the feedback we receive from our supporters and token holders. Since our last update on the release schedule for Nuklai-controlled allocations, the community provided great insights into how we can support the long-term growth and health of Nuklai's NAI token while ensuring our ecosystem remains resilient to future market conditions.
To ensure the success of NAI and the Nuklai ecosystem, and to align with the anticipated launch of NuklaiVM's mainnet, we are proactively implementing changes to NAI's vesting schedule. This move incorporates key feedback from our valued community. These adjustments extend beyond just Nuklai-controlled allocations and include all pre-sale allocations, ensuring a more balanced and supportive environment for the NAI ecosystem.
By taking these steps, we are reinforcing our commitment to NAI's sustainable development and the Nuklai platform's broader success.
Current Vesting Status
Depending on the allocation, between 30% and 41.6% of NAI tokens have already been vested. However, the remaining unvested tokens pose a challenge for attracting new buyers, potentially hindering the organic growth of the project in the coming year.
Typically, projects might choose to either extend the vesting period or accelerate token unlocks. We have gone a step further to offer all pre-sale participants a choice:
Presenting Tailored NAI Vesting Options
This update affects participants from the following rounds (note that the public allocation is excluded as it's nearly entirely vested already):
- Seed I
- Seed II (rALBT)
- Seed II (no rALBT)
- Strategic
- Private
Each participant will have two options:
- Lock Remaining Tokens: Lock a portion or all of their unvested tokens for an additional 12 months. After the 12-month lock period, any remaining tokens will be unlocked daily over the next 12 months.
- Unlock with Burn: Unlock a portion or all of their remaining tokens immediately, agreeing to burn a percentage of those tokens.
They can choose how many tokens they want to lock (option 1) and how many they want to unlock (option 2).
For every token burned, an equivalent amount will be drawn from Nuklai-controlled allocations exclusively dedicated to the community and a new hypergrowth phase. What this will look like will be disclosed shortly after this event, but we can already share that YOU (the DAO) will be in control of making this decision.
Burn Percentages by Allocation Type
Each allocation type has a different burn percentage, based on how many tokens are already vested:
- Seed I: 61.55%
- Seed II (rALBT): 53.12%
- Seed II (no rALBT): 50%
- Strategic: 53.2%
- Private: 51.35%
Example Scenario
Consider a participant with a 1 million NAI allocation in Seed II (no rALBT). They have vested 32.43% (324,000 NAI) so far but have yet to claim any tokens. In the new scenario, they will always have access to their vested 324,000 NAI tokens without any burn penalty.
For the remaining 676,000 tokens, they can choose to either lock them for 12 months or claim a portion now. If they choose to claim 200,000 of these tokens, they will burn 50% (or 100K NAI) of that amount. At the same time when executing this option, 100K NAI will be allocated from Nuklai's allocations for something special for the community.
Lock and Stake
Participants who lock their tokens gain access to exclusive, high-reward staking campaigns, allowing them to maximize their earnings while their tokens are securely locked.
12 Months to Takeoff: Mainnet, Adoption, and Industry Integration
The next 12 months will be a transformative period for Nuklai, as our mainnet is established and battle-tested, with enterprise adoption already on the horizon. Our testnet, HelixVM, is currently live and available at wallet.nuklaivm.com, providing a glimpse into the future of our ecosystem. Nuklai’s Business Development and Sales team is actively engaging with key sectors like Automotive, Agriculture, and Government. While these partnerships naturally require time to develop, the 12-month timeline is an exciting window for growth and industry integration!
New Claim Portal: Empowering Your Decisions
In the coming weeks, we’ll be introducing new vesting options that reflect our commitment to giving you greater control. During this time, scheduled unlocks on Fundrs and Sablier will be paused as we prepare for the launch of a new, user-friendly portal. This platform will allow you to seamlessly manage your claims, migrating from both Fundrs and Sablier.
Once the new claim portal is live, you’ll have 2 weeks to decide how much NAI to claim, putting the power in YOUR hands. And if you choose not to take action, your tokens will be automatically secured for 12 months, offering an extra layer of stability as we approach the exciting milestones ahead!
Looking Ahead: A Bright Future Together
As we look forward to these exciting updates and innovations, we are deeply grateful for the ongoing support and engagement from our community and partners. Your feedback and participation are instrumental in shaping the future of NAI and the Nuklai ecosystem. We are enthusiastic about the opportunities ahead and confident that these changes will enhance our collective journey. Stay tuned for more updates and join us as we continue to drive growth and success. Together, we are building something truly remarkable, and we’re thrilled to have you with us every step of the way. For any questions or additional support, don’t hesitate to reach out to us on Telegram or Discord—our team is here to assist you!
About Nuklai
Nuklai is a collaborative infrastructure provider for data ecosystems, integrating community-driven data analysis with data from successful modern businesses. Our platform connects data enthusiasts and institutional partners to harness untapped data and create new revenue streams.
We aim to unify the fragmented data landscape by offering a user-friendly, streamlined approach to sharing, requesting, and evaluating data for valuable insights, enhancing processes, accelerating new business opportunities, and empowering next-generation large language models and AI.
Follow Nuklai on X and join Telegram to stay updated on the latest Nuklai news and updates.
const ApiUrl = "https://api.nukl.ai/api/public/v1/datasets/:datasetId/queries";
const ApiKey = "[API_KEY]";
const DatasetId = "[DATASET_ID]";
const headers = {
"Content-Type": "application/json",
'authentication': ApiKey
}
ApiUrl = "https://api.nukl.ai/api/public/v1/datasets/:datasetId/queries"
ApiKey = "[API_KEY]"
DatasetId = "[DATASET_ID]"
headers = {
"Content-Type": "application/json",
"authentication": ApiKey
}
$ApiUrl = "https://api.nukl.ai/api/public/v1/datasets/:datasetId/queries";
$ApiKey = "[API_KEY]";
$DatasetId = "[DATASET_ID]";
$headers = [
"Content-Type: application/json",
"authentication: $ApiKey"
];
// @dataset represents your dataset rows as a table
const body = {
sqlQuery: "select * from @dataset limit 5",
}
@dataset represents your dataset rows as a table
body = {
"sqlQuery": "select * from @dataset limit 5"
}
// @dataset represents your dataset rows as a table
$body = [
"sqlQuery" => "select * from @dataset limit 5"
];
const ApiUrl = "https://api.nukl.ai/api/public/v1/datasets/:datasetId/queries";
const ApiKey = "[API_KEY]";
const DatasetId = "[DATASET_ID]";
const headers = {
"Content-Type": "application/json",
'authentication': ApiKey
}
// @dataset represents your dataset rows as a table
const body = {
sqlQuery: "select * from @dataset limit 5",
}
// make request
fetch(ApiUrl.replace(':datasetId', DatasetId), {
method: "POST",
headers: headers,
body: JSON.stringify(body), // convert to json object
})
.then((response) => response.json())
.then((data) => {
console.log(data);
})
.catch((error) => {
console.error(error);
});
import requests
import json
ApiUrl = "https://api.nukl.ai/api/public/v1/datasets/:datasetId/queries"
ApiKey = "[API_KEY]"
DatasetId = "[DATASET_ID]"
headers = {
"Content-Type": "application/json",
"authentication": ApiKey
}
# @dataset represents your dataset rows as a table
body = {
"sqlQuery": "select * from @dataset limit 5"
}
# make request
url = ApiUrl.replace(':datasetId', DatasetId)
try:
response = requests.post(url, headers=headers, data=json.dumps(body))
data = response.json()
print(data)
except requests.RequestException as error:
print(f"Error: {error}")
$ApiUrl = "https://api.nukl.ai/api/public/v1/datasets/:datasetId/queries";
$ApiKey = "[API_KEY]";
$DatasetId = "[DATASET_ID]";
$headers = [
"Content-Type: application/json",
"authentication: $ApiKey"
];
// @dataset represents your dataset rows as a table
$body = [
"sqlQuery" => "select * from @dataset limit 5"
];
// make request
$ch = curl_init(str_replace(':datasetId', $DatasetId, $ApiUrl));
curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode($body)); // convert to json object
curl_setopt($ch, CURLOPT_HTTPHEADER, $headers);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, TRUE);
$result = curl_exec($ch);
curl_close($ch);
echo $result;
curl -X POST 'https://api.nukl.ai/api/public/v1/datasets/[DATASET_ID]/queries' \
-H 'Content-Type: application/json' \
-H 'authentication: [API_KEY]' \
-d '{"sqlQuery":"select * from @dataset limit 5"}'
const ApiUrl = "https://api.nukl.ai/api/public/v1/datasets/:datasetId/queries/:jobId";
const ApiKey = "[API_KEY]";
const DatasetId = "[DATASET_ID]";
const JobId = "[JOB_ID]"; // retrieved from /queries request
const headers = {
"Content-Type": "application/json",
'authentication': ApiKey
}
// make request
fetch(ApiUrl.replace(':datasetId', DatasetId).replace(':jobId', JobId), {
method: "GET",
headers: headers
})
.then((response) => response.json())
.then((data) => {
console.log(data);
})
.catch((error) => {
console.error(error);
});
import requests
ApiUrl = "https://api.nukl.ai/api/public/v1/datasets/:datasetId/queries/:jobId"
ApiKey = "[API_KEY]"
DatasetId = "[DATASET_ID]"
JobId = "[JOB_ID]" # retrieved from /queries request
headers = {
"Content-Type": "application/json",
"authentication": ApiKey
}
# make request
url = ApiUrl.replace(':datasetId', DatasetId).replace(':jobId', JobId)
try:
response = requests.get(url, headers=headers)
data = response.json()
print(data)
except requests.RequestException as error:
print(f"Error: {error}")
$ApiUrl = "https://api.nukl.ai/api/public/v1/datasets/:datasetId/queries/:jobId";
$ApiKey = "[API_KEY]";
$DatasetId = "[DATASET_ID]";
$JobId = "[JOB_ID]"; // retrieved from /queries request
$headers = [
"Content-Type: application/json",
"authentication: $ApiKey"
];
// @dataset represents your dataset rows as a table
$body = [
"sqlQuery" => "select * from @dataset limit 5"
];
// make request
$ch = curl_init(str_replace(array(':datasetId', ':jobId'), array($DatasetId, $JobId), $ApiUrl));
curl_setopt($ch, CURLOPT_HTTPHEADER, $headers);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, TRUE);
$result = curl_exec($ch);
curl_close($ch);
echo $result;
curl 'https://api.nukl.ai/api/public/v1/datasets/[DATASET_ID]/queries/[JOB_ID]' \
-H 'Content-Type: application/json' \
-H 'authentication: [API_KEY]'