The Future Of Shopping Is Here

The World's first integrated E-Commerce and Supply Chain Ecosystem powered by Blockchain

ICOBench 4.9/5
Icorating 3.8 Hype Score
TrackICO 5/5
ICOMarks 9.4/10
WiserICO .6/5

What is Vanig

Vanig is an e-commerce startup powered by the blockchain. Our aim is to create a platform that changes the way e-commerce works. From manufacturer to consumers, we can apply the power of the blockchain to make shopping an amazing experience for everyone involved.

  • hyperledger sawtooth
  • Delivery
  • Features
  • Users
  • Rewards
  • Worried

Business Partners

Enterprise Ethereum Alliance
Bgroup Logistic
i-fashion Group
Aidant Tech
iCommerce Asia

Vanig Solution

An e-commerce platform built entirely around the blockchain. Our platform uses Hyperledger Sawtooth to build an e-commerce ecosystem that tackles key issues in e-commerce today.


Dealing with Middlemen

Long supply chains result in an increase in the number of hands a product changes, resulting in an increase in the final price of the product.


Reducing/Eliminating Middlemen

Vanig can effectively reduce the number of middlemen, resulting in the product becoming cheaper for you, and lucrative for the seller.


Long Payment Waiting Periods

If you buy a product from a seller today, the seller has to wait for a long while in order to get the payment for the product. On top of it, the seller loses money in the form of fees.


Instant Payment Transfers

On the Vanig platform, your payment is transferred to the seller immediately in the form of VANIG tokens. This enables the seller to ship your items faster and also results in fair margins for both Vanig and the Seller.


Lack Of Information On Raw Materials

Right now, the information about raw materials used in the manufacture of a product is hidden in data silos that are hard to open without formal investigation or other long tedious means.


Complete Transparency

The Vanig platform can store detailed vital information about the raw materials used in the manufacturing of a product, enabling complete transparency about how the product has been made.


Fractured Tracking

Tracking the source of all the materials used to make a product along with the product is insanely difficult, since it is fractured and split across multiple shipping services.


Total Tracking

All the transportation records are stored in the blockchain forever, allowing you to track your orders more efficiently, from manufacturing to delivery.

  • Dealing with Middlemen

    ProblemDealing with Middlemen

    SolutionReducing/Eliminating Middlemen

  • Long Payment Waiting Periods

    ProblemLong Payment Waiting Periods

    SolutionInstant Payment Transfers

  • Lack of infomation on raw materials

    ProblemLack of infomation on raw materials

    SolutionComplete Transparency

  • Fractured Tracking

    ProblemFractured Tracking

    SolutionTotal Tracking

Introducing the Vanig Marketplace

A blockchain-powered marketplace which connects buyers and sellers directly, cutting out the middleman in the process. Fast, efficient and reliable.

MVP Demo Video
  • Purchase using VANIG tokens, cryptocurrencies or Fiat!
  • Products handpicked by experts & AI Algorithms.
  • Prices that are hard to resist.
  • Information about where products come from.
  • Verified Sellers and Reviews.
  • Rewards for every purchase in form of tokens!

Vanig Technical Architecture

Public Blockchain

Private Blockchain

Vanig Technical Architecture

Patent Pending Technology Patent Application #15936458

Integrated E-Commerce and Supply Chain Solution using Blockchain

Patent defines an integrate e-commerce and supply chain solution using blockchain Technology that addresses several significant present day challenges and inefficiencies; simplifies the e-commerce experience; eliminates intermediaries and manual processes in the supply chain; shortens recall process and timelines for manufacturers and retailers, providing real-time product visibility through to the consumer.

Don Quartiere

Don Quartiere

Chief Solutions Architect

Vanig is passionately integrating e-commerce, supply chain, and token economics into a robust platform. The platform incorporates identity, comprehensive product classification details, IoT, and event/geolocation into its blockchain platform based on international standards, from the producer to consumer. The chain of custody, linking the digital to the physical on a trustless decentralized ledger, provides knowledge-based options to all Vanig supply chain stakeholders, including the importing countries customs agencies.

Alan Wong

Alan Wong

Market Strategist

Vanig has developed a prototype to bring the eCommerce and supply chain process onto a blockchain. The platform will allow sharing of information between participants on a secure blockchain-based network and automates processes such as a bill of lading and fix inefficiencies due to double marginalization and information asymmetry. Vanig's prototype is built on hybrid blockchain using Hyperledger Sawtooth and Ethereum(ETH). Blockchain increases efficiency along the entire supply chain, logistics and settlement process.

Jeremy Khoo

Jeremy Khoo

Retail Strategist

The Vanig solution is built on the blockchain, which is a perfect use-case and marries the best aspects of the blockchain with the biggest issues in supply-chain. The problems of multiple intermediaries, high fees, low visibility and lack of tracking is tackled by a scalable proprietary blockchain solution.

By harnessing cutting-edge technology which was non-existent in 2008, I believe 2018 to be the year where supply-chain management gets disrupted by Vanig, leading to a more level-playing field among brands and marketplaces.

Dan Ramirez

Dan Ramirez


It is a pleasure to work for Vanig as CEO. Everyday, I see the company expand and heighten to a growth rate that I would have never imagined. Each member of the team adds a piece of the puzzle contributing each day moving the project forward with carefully planned steps.

When it comes to eCommerce and supply chain, Vanig is the first platform which integrates supply chain, ecommerce and a payment system in the same solution. Using artificial intelligence and machine learning, the Vanig platform will revolutionize shopping experiences across the world.

Vanig Features

Vanig is built for end users, customers, sellers and supply chain operations. Vanig is built to be beneficial for everyone involved with us.


Any successful project needs a plan of action in place in order to ensure that it sees through the finish line. With careful consideration, we have laid out the following plan to ensure Vanig's success:

Mar 2017

Vanig concept is born

May 2017

Core team was formed, Business process and Technology solution framework created

Jun 2017

E-commerce Development kicked off

Dec 2017

Build Smart Contract and Blockchain components

Feb 2018

Integration between e-commerce and Blockchain

July 2018

VANIG Token Generation Event

Dec 2018

Launch e-commerce Alpha Version ecosystem - Open up registration for Vanig team & community

Mar 2019

Launch e-commerce beta version ecosystem - On-board up to 1000 supply chain Asia Manufacturers/Sellers to Ecosystem

Jun 2019

Launch Vanig e-commerce and Mobile App in Asia - Philippines & Malaysia Consumers for fashion, furniture & appliances

Sep 2019

Expand categories to Toys, Hobby, DIY; On-board 5000 Sellers to ecosystem

Dec 2019

Launch Vanig to Vietnam; Vanig 2.0 Product release

Jun 2020

Launch of Singapore 10,000 Sellers to Ecosystem

Dec 2020

HongKong Launch, Vanig 3.0 Product release

Jun 2021

Vanig Launch in Indonesia

Dec 2021

India Launch

Jun 2022

On-board 25,000 Sellers to Ecosystem

Jun 2024

On-board 100,000 Sellers followed by rest of world subsequent roll out's - US, UK, Germany, France, South Korea, Canada, Russia, Brazil & Japan

In The Media

Coin Idol
Yahoo Finance
New York Business Journal
Market Watch
Markets Insider
Latin Business Today

Token Sale

The sale of VANIG tokens will enable us to build a platform that is beneficial to everyone, from manufacturers to consumers. On buying VANIG tokens, you are contributing towards a system that is not only built to last, but is also resilient. On top of that, we'll give you a bonus if you're early!

Pre Sale Now Open

Ends On 21 Aug 2018

Pre Sale

15 August 2018 7 Days

30% Bonus

Hard Cap $5M


22 August 2018 7 Days

25% Bonus

Hard Cap $5M


29 August 2018 7 Days

20% Bonus

Hard Cap $4M


5 September 2018 7 Days

10% Bonus

Hard Cap $2M


12 September 2018 7 Days

5% Bonus

Hard Cap $1M


19 September 2018 7 Days

0% Bonus

Hard Cap $1M

Token symbol VANIG
Sale Start 15 August 2018
Sale End 25 September 2018
Maximum Supply 225 Million
Sold to Public 141 Million
Private Sale 2 Million USD
Pre-Sale 5 Million USD
Main Sale 13 Million USD
Soft Cap 2 Million USD
Hard Cap 20 Million USD
Accepted Currencies ETH, BTC, LTC, USD
Minimum Contribution 0.1 ETH

Token Distribution

  • 63%
    Open Market
  • 15%
    Team Tokens*
  • 12%
    Vanig Rewards and Incentives
  • 5%
    Referral & Bounty Program
  • 3%
    Advisors & Partners#
  • 2%
Open Market Team Tokens Product Incentives Referral & Bounty Program Advisory Legal

*Team Tokens - 4 years lock down with first release after 12 months of TGE completion. 15% of tokens released every 6 months and last 10% at end of 4th Year.

#Advisors and Partners - 1 year lock down with first release of 25% of tokens after 3 months of TGE completion. 25% of tokens released every 3 months thereafter.

✦Legal - 2 Year lock down with first release after 6 months of TGE completion, 25% of tokens released every 6 months thereafter.

✝Incentives - 4 years incentive program, capped to release 25% every year. Arrived based on business plan and customer acquisition rate.

Operating Budget

Operating Budget
  • 30%
    Business Dev & Ops
  • 30%
    Marketing and Sales
  • 20%
    Admin and Operation
  • 10%
    Legal and Advisory
  • 10%

Providing "50% Hedging Protection" for 6 months

The buyer can claim 50% of his/her investment within the hedging period if:

The rate of VANIG token falls within the first six months after getting listed

Vanig token is not listed on exchanges

Vanig turns out to be a scam or closed

Buy Hedge Token

Token Velocity & Demand

Dual Token

Provides stable cryptoeconomic shopping experience for consumers

Vanig Rewards program

Stores pay Vanig a commission for sending you their way, and Vanig shares the commission with you as Cash Back in Vanig Tokens

Token Burn

All unsold tokens post the Token Sale will be burned in a publicly verifiable way

Token Lock Down Period

Team, Advisor and Legal has a duration of lock up period

Token Sale Partners

Token Fest
TrackICO - provider of information about the best ICOs
ICO Guru
ICO Rating
ICO Daily

Meet The Team

Vanig Smart Contract

pragma solidity 0.4.23;

 * @title SafeMath
 * @dev Math operations with safety checks that throw on error
library SafeMath {

    * @dev Multiplies two numbers, throws on overflow.
    function mul(uint256 a, uint256 b) internal pure returns (uint256) {
        if (a == 0) {
            return 0;
        uint256 c = a * b;
        assert(c / a == b);
        return c;

    * @dev Integer division of two numbers, truncating the quotient.
    function div(uint256 a, uint256 b) internal pure returns (uint256) {
        // assert(b > 0); // Solidity automatically throws when dividing by 0
        uint256 c = a / b;
        // assert(a == b * c + a % b); // There is no case in which this doesn't hold
        return c;

    * @dev Subtracts two numbers, throws on overflow (i.e. if subtrahend is greater than minuend).
    function sub(uint256 a, uint256 b) internal pure returns (uint256) {
        assert(b <= a);
        return a - b;

    * @dev Adds two numbers, throws on overflow.
    function add(uint256 a, uint256 b) internal pure returns (uint256) {
        uint256 c = a + b;
        assert(c >= a);
        return c;

 * @title ERC20Basic
 * @dev Simpler version of ERC20 interface
 * @dev see
contract ERC20Basic {
    function totalSupply() public view returns (uint256);
    function balanceOf(address who) public view returns (uint256);
    function transfer(address to, uint256 value) public returns (bool);
    event Transfer(address indexed from, address indexed to, uint256 value);

 * @title Basic token
 * @dev Basic version of StandardToken, with no allowances.
contract BasicToken is ERC20Basic {
    using SafeMath for uint256;

    mapping(address => uint256) internal balances;

    uint256 internal totalSupply_;

    * @dev total number of tokens in existence
    function totalSupply() public view returns (uint256) {
        return totalSupply_;

    * @dev transfer token for a specified address
    * @param _to The address to transfer to.
    * @param _value The amount to be transferred.
    function transfer(address _to, uint256 _value) public returns (bool) {
        require(_to != address(0));
        require(_value <= balances[msg.sender]);

        // SafeMath.sub will throw if there is not enough balance.
        balances[msg.sender] = balances[msg.sender].sub(_value);
        balances[_to] = balances[_to].add(_value);
        emit Transfer(msg.sender, _to, _value);
        return true;

    * @dev Gets the balance of the specified address.
    * @param _owner The address to query the the balance of.
    * @return An uint256 representing the amount owned by the passed address.
    function balanceOf(address _owner) public view returns (uint256 balance) {
        return balances[_owner];

 * @title ERC20 interface
 * @dev see
contract ERC20 is ERC20Basic {
    function allowance(address owner, address spender) public view returns (uint256);
    function transferFrom(address from, address to, uint256 value) public returns (bool);
    function approve(address spender, uint256 value) public returns (bool);
    event Approval(address indexed owner, address indexed spender, uint256 value);

 * @title Standard ERC20 token
 * @dev Implementation of the basic standard token.
 * @dev
 * @dev Based on code by FirstBlood:
contract StandardToken is ERC20, BasicToken {

    mapping (address => mapping (address => uint256)) internal allowed;

     * @dev Transfer tokens from one address to another
     * @param _from address The address which you want to send tokens from
     * @param _to address The address which you want to transfer to
     * @param _value uint256 the amount of tokens to be transferred
    function transferFrom(address _from, address _to, uint256 _value) public returns (bool) {
        require(_to != address(0));
        require(_value <= balances[_from]);
        require(_value <= allowed[_from][msg.sender]);

        balances[_from] = balances[_from].sub(_value);
        balances[_to] = balances[_to].add(_value);
        allowed[_from][msg.sender] = allowed[_from][msg.sender].sub(_value);
        emit Transfer(_from, _to, _value);
        return true;

     * @dev Approve the passed address to spend the specified amount of tokens on behalf of msg.sender.
     * Beware that changing an allowance with this method brings the risk that someone may use both the old
     * and the new allowance by unfortunate transaction ordering. One possible solution to mitigate this
     * race condition is to first reduce the spender's allowance to 0 and set the desired value afterwards:
     * @param _spender The address which will spend the funds.
     * @param _value The amount of tokens to be spent.
    function approve(address _spender, uint256 _value) public returns (bool) {
        allowed[msg.sender][_spender] = _value;
        emit Approval(msg.sender, _spender, _value);
        return true;

     * @dev Function to check the amount of tokens that an owner allowed to a spender.
     * @param _owner address The address which owns the funds.
     * @param _spender address The address which will spend the funds.
     * @return A uint256 specifying the amount of tokens still available for the spender.
    function allowance(address _owner, address _spender) public view returns (uint256 remaining) {
        return allowed[_owner][_spender];

     * approve should be called when allowed[_spender] == 0. To increment
     * allowed value is better to use this function to avoid 2 calls (and wait until
     * the first transaction is mined)
     * From MonolithDAO Token.sol
    function increaseApproval (address _spender, uint _addedValue) public returns (bool success) {
        allowed[msg.sender][_spender] = allowed[msg.sender][_spender].add(_addedValue);
        emit Approval(msg.sender, _spender, allowed[msg.sender][_spender]);
        return true;

    function decreaseApproval (address _spender, uint _subtractedValue) public returns (bool success) {
        uint oldValue = allowed[msg.sender][_spender];
        if (_subtractedValue > oldValue) {
            allowed[msg.sender][_spender] = 0;
        } else {
            allowed[msg.sender][_spender] = oldValue.sub(_subtractedValue);
        emit Approval(msg.sender, _spender, allowed[msg.sender][_spender]);
        return true;

 * @title SafeERC20
 * @dev Wrappers around ERC20 operations that throw on failure.
 * To use this library you can add a `using SafeERC20 for ERC20;` statement to your contract,
 * which allows you to call the safe operations as `token.safeTransfer(...)`, etc.
library SafeERC20 {
    function safeTransfer(ERC20Basic token, address to, uint256 value) internal {
        assert(token.transfer(to, value));

    function safeTransferFrom(ERC20 token, address from, address to, uint256 value) internal {
        assert(token.transferFrom(from, to, value));

    function safeApprove(ERC20 token, address spender, uint256 value) internal {
        assert(token.approve(spender, value));

 * @title TokenTimelock
 * @dev TokenTimelock is a token holder contract that will allow a
 * beneficiary to extract the tokens after a given release time
contract TokenTimelock {
    using SafeERC20 for ERC20Basic;

    // ERC20 basic token contract being held
    ERC20Basic public token;

    // beneficiary of tokens after they are released
    address public beneficiary;

    // timestamp when token release is enabled
    uint64 public releaseTime;

    constructor(ERC20Basic _token, address _beneficiary, uint64 _releaseTime) public {
        require(_releaseTime > uint64(block.timestamp));
        token = _token;
        beneficiary = _beneficiary;
        releaseTime = _releaseTime;

     * @notice Transfers tokens held by timelock to beneficiary.
    function release() public {
        require(uint64(block.timestamp) >= releaseTime);

        uint256 amount = token.balanceOf(this);
        require(amount > 0);

        token.safeTransfer(beneficiary, amount);

 * @title Burnable Token
 * @dev Token that can be irreversibly burned (destroyed).
contract BurnableToken is BasicToken {

  event Burn(address indexed burner, uint256 value);

   * @dev Burns a specific amount of tokens.
   * @param _value The amount of token to be burned.
  function burn(uint256 _value) public {
    _burn(msg.sender, _value);

  function _burn(address _who, uint256 _value) internal {
    require(_value <= balances[_who]);
    // no need to require value <= totalSupply, since that would imply the
    // sender's balance is greater than the totalSupply, which *should* be an assertion failure

    balances[_who] = balances[_who].sub(_value);
    totalSupply_ = totalSupply_.sub(_value);
    emit Burn(_who, _value);
    emit Transfer(_who, address(0), _value);
 * @title TokenVault
 * @dev TokenVault is a token holder contract that will allow a
 * beneficiary to spend the tokens from some function of a specified ERC20 token
contract TokenVault {
    using SafeERC20 for ERC20;

    // ERC20 token contract being held
    ERC20 public token;

    constructor(ERC20 _token) public {
        token = _token;

     * @notice increase the allowance to the full amount of tokens held
    function fillUpAllowance() public {
        uint256 amount = token.balanceOf(this);
        require(amount > 0);

        token.approve(token, amount);

contract Owned {
    address public owner;

    constructor() public {
        owner = msg.sender;

    modifier onlyOwner {
        require(msg.sender == owner);

 * @title TokenVesting
 * @dev A token holder contract that can release its token balance gradually like a
 * typical vesting scheme, with a cliff and vesting period. Optionally revocable by the
 * owner.
contract TokenVesting is Owned {
    using SafeMath for uint256;
    using SafeERC20 for ERC20Basic;

    event Released(uint256 amount);
    event Revoked();

    // beneficiary of tokens after they are released
    address public beneficiary;

    uint256 public cliff;
    uint256 public start;
    uint256 public duration;

    bool public revocable;

    mapping (address => uint256) public released;
    mapping (address => bool) public revoked;

     * @dev Creates a vesting contract that vests its balance of any ERC20 token to the
     * _beneficiary, gradually in a linear fashion until _start + _duration. By then all
     * of the balance will have vested.
     * @param _beneficiary address of the beneficiary to whom vested tokens are transferred
     * @param _cliff duration in seconds of the cliff in which tokens will begin to vest
     * @param _duration duration in seconds of the period in which the tokens will vest
     * @param _revocable whether the vesting is revocable or not
    constructor(address _beneficiary, uint256 _start, uint256 _cliff, uint256 _duration, bool _revocable) public {
        require(_beneficiary != address(0));
        require(_cliff <= _duration);

        beneficiary = _beneficiary;
        revocable = _revocable;
        duration = _duration;
        cliff = _start.add(_cliff);
        start = _start;

     * @notice Transfers vested tokens to beneficiary.
     * @param token ERC20 token which is being vested
    function release(ERC20Basic token) public {
        uint256 unreleased = releasableAmount(token);

        require(unreleased > 0);

        released[token] = released[token].add(unreleased);

        token.safeTransfer(beneficiary, unreleased);

        emit Released(unreleased);

     * @notice Allows the owner to revoke the vesting. Tokens already vested
     * remain in the contract, the rest are returned to the owner.
     * @param token ERC20 token which is being vested
    function revoke(ERC20Basic token) public onlyOwner {

        uint256 balance = token.balanceOf(this);

        uint256 unreleased = releasableAmount(token);
        uint256 refund = balance.sub(unreleased);

        revoked[token] = true;

        token.safeTransfer(owner, refund);

        emit Revoked();

     * @dev Calculates the amount that has already vested but hasn't been released yet.
     * @param token ERC20 token which is being vested
    function releasableAmount(ERC20Basic token) public view returns (uint256) {
        return vestedAmount(token).sub(released[token]);

     * @dev Calculates the amount that has already vested.
     * @param token ERC20 token which is being vested
    function vestedAmount(ERC20Basic token) public view returns (uint256) {
        uint256 currentBalance = token.balanceOf(this);
        uint256 totalBalance = currentBalance.add(released[token]);

        if (now < cliff) {
            return 0;
        } else if (now >= start.add(duration) || revoked[token]) {
            return totalBalance;
        } else {
            return totalBalance.mul(now.sub(start)).div(duration);

contract VanigToken is BurnableToken, Owned {
    string public constant name = "Vanig";
    string public constant symbol = "VANG";
    uint8 public constant decimals = 18;

    /// Maximum tokens to be allocated (300 million)
    uint256 public constant HARD_CAP = 300000000 * 10**uint256(decimals);

    /// The owner of this address will distrbute the locked and vested tokens
    address public vanigAdminAddress;

    /// This vault holds are the Vanig team
    TokenVault public teamTokensVault;

    /// This vault holds the Vanig Incentives tokens
    TokenVault public incentivesTokensVault;

    /// This vault holds the Vanig Advisory tokens
    TokenVault public advisoryTokensVault;

    /// This vault holds Vanig Legal tokens
    TokenVault public legalTokensVault;

    /// Store the vesting contracts addresses
    mapping(address => address) public vestingOf;

    /// This address is used to keep the tokens for sale
    address public saleTokensAddress;

    /// This address is used to keep the Vanig Referral Program
    address public referralsTokensAddress;

    /// when the token sale is closed, the trading is open
    bool public saleClosed = false;

    /// Only allowed to execute before the token sale is closed
    modifier beforeSaleClosed {

    modifier onlyAdmin {
        require(msg.sender == vanigAdminAddress);

    constructor(address _vanigAdminAddress, address _referralsTokensAddress, address _saleTokensAddress) public {
        require(_vanigAdminAddress != address(0));
        require(_referralsTokensAddress != address(0));
        require(_saleTokensAddress != address(0));

        vanigAdminAddress = _vanigAdminAddress;
        referralsTokensAddress = _referralsTokensAddress;
        saleTokensAddress = _saleTokensAddress;

        /// Maximum tokens to be allocated on the sale
        /// 180M VANG tokens
        uint256 saleTokens = 180000000 * 10**uint256(decimals);
        totalSupply_ = saleTokens;
        balances[saleTokensAddress] = saleTokens;

        /// Referrals Program tokens - 15 million
        uint256 referralsTokens = 15000000 * 10**uint256(decimals);
        totalSupply_ = totalSupply_.add(referralsTokens);
        balances[referralsTokensAddress] = referralsTokens;

    function createVestableTokens() internal onlyOwner {
            /// Team tokens - 54 million
            uint256 teamTokens = 54000000 * 10**uint256(decimals);
            totalSupply_ = totalSupply_.add(teamTokens);
            teamTokensVault = new TokenVault(this);
            balances[teamTokensVault] = teamTokens;

            /// Incentives tokens - 39 million
            uint256 incentivesTokens = 39000000 * 10**uint256(decimals);
            totalSupply_ = totalSupply_.add(incentivesTokens);
            incentivesTokensVault = new TokenVault(this);
            balances[incentivesTokensVault] = incentivesTokens;

            /// Advisory tokens - 6 million
            uint256 advisoryTokens = 6000000 * 10**uint256(decimals);
            totalSupply_ = totalSupply_.add(advisoryTokens);
            advisoryTokensVault = new TokenVault(this);
            balances[advisoryTokensVault] = advisoryTokens;

            /// Legal tokens - 6 million
            uint256 legalTokens = 6000000 * 10**uint256(decimals);
            totalSupply_ = totalSupply_.add(legalTokens);
            legalTokensVault = new TokenVault(this);
            balances[legalTokensVault] = legalTokens;

    function vestTokens(address _fromVault, uint256 _tokensAmount, address _beneficiary, uint256 _start,
    uint256 _cliff, uint256 _duration, bool _revocable) external onlyAdmin {
        TokenVesting vesting = TokenVesting(vestingOf[_beneficiary]);
        if(vesting == address(0)) {
            vesting = new TokenVesting(_beneficiary, _start, _cliff, _duration, _revocable);
            vestingOf[_beneficiary] = address(vesting);

        if(this.allowance(_fromVault, address(this)) < _tokensAmount) {
        require(this.transferFrom(_fromVault, vesting, _tokensAmount));

    /// @dev check the locked balance of an owner
    function lockedBalanceOf(address _owner) public view returns (uint256) {
        return balances[vestingOf[_owner]];

    /// @dev check the locked but releaseable balance of an owner
    function releaseableBalanceOf(address _owner) public view returns (uint256) {
        return TokenVesting(vestingOf[_owner]).vestedAmount(this);

    /// @dev release all unlocked tokens of an owner
    function releaseTokens(address _owner) public {

    /// @dev get the TokenTimelock contract address for an owner
    function vestingOf(address _owner) public view returns (address) {
        return vestingOf[_owner];

    /// @dev Close the token sale
    function closeSale() public onlyOwner beforeSaleClosed {
        saleClosed = true;

    /// @dev Trading limited - requires the token sale to have closed
    function transferFrom(address _from, address _to, uint256 _value) public returns (bool) {
        if(saleClosed || msg.sender == vanigAdminAddress) {
            return super.transferFrom(_from, _to, _value);
        return false;

    /// @dev Trading limited - requires the token sale to have closed
    function transfer(address _to, uint256 _value) public returns (bool) {
        if(saleClosed || msg.sender == owner || (msg.sender == saleTokensAddress && _to == owner)) {
            return super.transfer(_to, _value);
        return false;
View Code on Github


Ready to dive deeper and learn more about our project? Checkout the whitepaper for detailed information on Vanig’s technical infrastructure and business plan.

Frequently asked questions

What is Vanig?

Vanig is an integratede-commerce platform and supply chain ecosystem that is powered by the blockchain. We aim to solve some of the major inefficiencies and challenges with the existing supply chain and e-commerce platforms.

What are the problems and challenges that Vanig addresses?

Vanig is aiming to solve the following major problems in the supply chain and e-commerce space.

  • Lack of transparency and full visibility in the supply chain
  • Too many intermediaries and manual paper work
  • Static or non-existent inventory management
  • Inefficient tracking of products
  • High selling fees on e-commerce platforms for sellers
  • Lack of provenance information for products for buyers

For a detailed list of all problems that Vanig addresses please check our whitepaper

What is the Vanig e-commerce Platform?

Vanig is building an e-commerce platform from the ground up. The Vanig e-commerce platform will be beneficial to all participants. The sellers will enjoy benefit of lesser selling fees (compared to other major e-commerce players) and instant payments, and the buyers will enjoy the benefits of buying trusted products, paying with different payment methods (including VANIG tokens) and be rewarded for purchases on the platform.

What are the major differences between Vanig and other e-commerce players?

Here are the key benefits of Vanig over other players.

What blockchain technology does Vanig use?

Vanig is built on Hyperledger Sawtooth. Hyperledger Sawtooth has some unique advantages that lends itself for Vanig’s supply chain solution. Some of them are –

  • Private networks with the Sawtooth permissioning features
  • On-chain governance – Utilize smart contracts to vote on blockchain configuration settings such as the allowed participants and smart contracts
  • Advanced transaction execution engine – Process transactions in parallel to accelerate block creation and validation. This will help scalability when we have large volume of transactions processed in the Vanig e-commerce platform.
  • Support for Ethereum – Run solidity smart contracts and integrate with Ethereum.

For more information refer our Whitepaper.

Vanig is a member of the Enterprise Ethereum Alliance.

Do you have a working demo or MVP?

Vanig’s E-commerce platform will be modern and sleek, it will have easy navigation for the buyers and sellers, Vanig will have AI/ML powered platform that will track buyers, sellers and products and will play a key part in making the platform trustworthy for everyone involved.

We have an early demo of the e-commerce platform MVP that you can try out now. Head over here for information on MVP, guide and link to try it out ->

We welcome you to try it out and let us know if you have any feedback.

Where can I find information on Vanig’s roadmap?

Vanig’s journey started in early 2017, we have since then come a long way from assembling best in class team and advisors to building the solution framework and MVP.

We are launching the Token sale in July 2018, our e-commerce platform's alpha version in December 2018 and launch the platform for South East Asia in March 2019.

We are excited to be on this exciting journey to build Vanig as we envision it. Please check our whitepaper for a detailed roadmap.

When is the token sale, how many tokens are being sold and what are the timelines?

Vanig’s Token Sale Generation event will start in June 2018, it will have a Pre-Sale followed by 5 Token Sale stages. Each stage will have varying levels of bonus tokens rewarding early participants more.

Here is the key token sale information.

Token symbol VANIG
Sale Start 15 August 2018
Sale End 25 September 2018
Maximum Supply 225 Million
Sold to Public 141 Million
Private Sale 2 Million USD
Pre-Sale 5 Million USD
Main Sale 13 Million USD
Soft Cap 2 Million USD
Hard Cap 20 Million USD
Accepted Currencies ETH, BTC, LTC, USD
Minimum Contribution 0.1 ETH

Who can participate in the token sale?

Our token sale is open for global participation, people from all countries except the ones listed below are welcome to participate in the token sale. However, we do recommend that you review any country specific legislation to ensure you are abiding by the rules of your country.

People from US are not allowed to participate in this token sale. If you are a resident or citizen of the US, you will be identified through the KYC process and any participation in the token sale will be reversed.

What is the use of the Vanig Token?

VANIG tokens will be used throughout our e-commerce and supply chain for paying for transactions, as incentives for buyers and sellers for activity on the platform, and as rewards through the Vanig Loyalty Rewards program in the e-commerce platform