|
||||||||||||||||||||||||||
| SEC Info℠ | | | Home | | | Search | | | My Interests | | | Help | | | Sign In | | | Please Sign In | |||||||
|
||||||||||||||||||||||||||
As Of Filer Filing For·On·As Docs:Size Issuer Filing Agent 8/19/19 Inx Ltd F-1 37:4.5M Edgar Agents LLC/FA |
Document/Exhibit Description Pages Size
1: F-1 Registration Statement by a Foreign Issuer HTML 1.15M
2: EX-3.1 Memorandum of Association of the Company HTML 15K
3: EX-3.2 Second Amended and Restated Articles of HTML 207K
Association of the Company, as Currently in Effect
4: EX-4.1 Form of Inx Token Purchase Agreement HTML 120K
5: EX-4.2 Form of Waiver and Subordination Undertaking HTML 28K
6: EX-4.3 Smart Contract HTML 47K
7: EX-4.4 Inx Smart Contract Description V.2.2, Dated July HTML 31K
7, 2019
8: EX-10.1 Founders' Agreement Dated September 1, 2017, HTML 42K
Between Triple-V (1999) Ltd. and A-Labs Finance
and Advisory Ltd.
17: EX-10.10 Amended and Restated Executive Services Agreement HTML 38K
Dated June 25, 2018 Among Fidelis LLC, Inx Limited
and Inx Services, Inc.
18: EX-10.11 Amended and Restated Consultancy Agreement Dated HTML 59K
June 25, 2018 Between Ms. Maia Naor and Inx
Limited
19: EX-10.12 Services Agreement Dated May 1, 2018 Between HTML 40K
Shiran Communications Ltd. and Inx Limited
20: EX-10.13 Amended and Restated Consultancy Agreement Dated HTML 53K
June 25, 2018 Between Mr. Jonathan Azeroual and
Inx Limited
21: EX-10.14 Amended and Restated Executive Employment HTML 86K
Agreement Dated June 25, 2018 Between Mr. Alan
Silbert and Inx Services Inc
22: EX-10.15 Services Agreement Dated March 8, 2018 Between HTML 34K
Bentley Limited and Inx Limited
23: EX-10.16 Amendment to Services Agreement Dated September 6, HTML 19K
2018 Between Bentley Limited and Inx Limited
24: EX-10.17 Second Amendment to Services Agreement Dated HTML 19K
November 30, 2018 Between Bentley Limited and Inx
Limited
25: EX-10.18 Amended and Restated Letter of Invitation Dated HTML 31K
June 25, 2018 Between Mr. David Weild and Inx
Limited
26: EX-10.19 Loan Agreement Dated November 27, 2017 Between Ms. HTML 28K
Maia Naor and Inx Limited
9: EX-10.2 Addendum to Founders' Agreement Dated September HTML 18K
27, 2017 Between Triple-V (1999) Ltd. and A-Labs
Finance and Advisory Ltd.
27: EX-10.20 Loan Agreement Dated November 27, 2017 Between Ms. HTML 28K
Ayelet Horn and Inx Limited
28: EX-10.21 Loan Agreement Dated November 27, 2017 Between Mr. HTML 29K
Yaniv Segev and Inx Limited
29: EX-10.22 Letter of Invitation Dated July 10, 2018 Mr. HTML 28K
Nicholas Thadaney and Inx Limited
30: EX-10.23 Letter of Invitation Dated August 20, 2018 Mr. HTML 27K
Haim Ashar and Inx Limited
31: EX-10.24 Letter of Invitation Dated September 21, 2018 Mr. HTML 27K
Thomas Lewis and Inx Limited
32: EX-10.25 Form of Custodial Services Agreement Between Inx HTML 137K
Digital Inc. and Bitgo Trust Company
33: EX-10.26 Form of Subscription Escrow Agreement Between Inx HTML 57K
Limited and Metropolitan Commercial Bank, as
Escrow Agent
34: EX-10.27 Simple Agreement for Future Equity, Dated April HTML 39K
25, 2019, Between Shy Datika and Inx Limited
35: EX-10.28 Simple Agreement for Future Equity, Dated April HTML 38K
25, 2019, Between A-Labs Finance and Advisory Ltd.
and Inx Limited
10: EX-10.3 Addendum 2 to Founders' Agreement Dated December HTML 20K
31, 2017 Between Triple-V (1999) Ltd. and A-Labs
Finance and Advisory Ltd.
11: EX-10.4 Amended and Restated Consultancy Agreement Dated HTML 54K
June 25, 2018 Between Triple-V (1999) Ltd. and Inx
Limited
12: EX-10.5 Financial Services Agreement Dated December 26, HTML 25K
2017 Between Insight Finance Ltd. and Inx Limited
13: EX-10.6 Second Amended and Restated Engagement Agreement HTML 72K
Dated December 31, 2017 Between A-Labs Finance and
Advisory Ltd. and Inx Limited
14: EX-10.7 Amendment to the Second Amended and Restated HTML 23K
Engagement Agreement Dated January 31, 2018,
Between A-Labs Finance and Advisory Ltd. and Inx
Limited
15: EX-10.8 Amended and Restated Software Services Agreement HTML 134K
Dated May 9, 2018, by and Between Y. Singer
Technologies Ltd. (Committed) and Inx Limited
16: EX-10.9 Amendment to Amended and Restated Software HTML 18K
Services Agreement Dated June 27, 2018, by and
Between Y. Singer Technologies Ltd. (Committed)
and Inx Limited
36: EX-21.1 List of Subsidiaries of the Registrant HTML 14K
37: EX-23.1 Consent of Kost Forer Gabbay & Kasierer, HTML 16K
Independent Registered Public Accounting Firm
Exhibit 4.4
INX Smart Contract
Description
V.2.2
C:
C: 1
Introduction
“Smart contracts” are self-executing rules in a programmable computer language on the blockchain that are enforced by the participants of the blockchain’s network. The Ethereum blockchain is an open-source, public, blockchain-based distributed computing platform that allows for decentralized programming of applications and the use of smart contracts. Many blockchain assets are developed in accordance with the “ERC20” standard, which allows developers to program them to include smart contracts that function within the Ethereum ecosystem.
The INX Token is an ERC20 smart contract. Material features of the INX Token included in the source code are the following:
| 1. | Designation and Number of Tokens. The INX Tokens of INX Limited (the “Company”) shall be designated as “INX Tokens.” The number of authorized INX Tokens is 200,000,000. The technical limits on the fractional division of INX Tokens is to eighteen decimal places (0.000000000000000001). The INX Token is an ERC20 blockchain asset that is programmed using a smart contract written in Solidity that is compatible with the Ethereum blockchain. The ERC-20 standard is a technical standard used for smart contracts on the Ethereum blockchain so that tokens can be transferred to a digital wallet. | |
| 2. | To be deemed to be a holder of record of INX Tokens, a holder must (a) register an Ethereum wallet with the Company to be included on the Whitelist Database and (b) have the public wallet address of this Ethereum wallet recorded on the “INX Token distributed ledger” as the holder INX Tokens. | |
| 3. | The “Whitelist Database” is a database stored on the data section of the INX Token smart contract. The purpose of the Whitelist Database is to validate decentralized transfers of the INX Token. The Whitelist Database contains a list of individuals and entities that have satisfied the Company’s KYC/AML compliance procedures and thus are eligible to hold INX Tokens. In order for an Ethereum wallet address to be included in the Whitelist Database, the prospective holder of record of the INX Tokens must have completed know your customer and anti-money laundering (“KYC/AML”) compliance procedures, or other similar procedures, to the satisfaction of the Company, or an agent of the Company that is expressly authorized in writing by the Company. | |
| The INX Token smart contract incorporates our Whitelist Database, which restricts the transfer of INX Tokens such that a transfer is not executed and recorded on the INX Token Distributed Ledger unless both the digital wallet addresses of the sender and receiver are listed in the Whitelist Database. | ||
| 4. | The “INX Token distributed ledger” references the ledger of ownership of INX Tokens that is recorded on the Ethereum blockchain. The INX Token distributed ledger records the public wallet addresses of all Ethereum wallets that hold INX Tokens and the balance of INX Tokens in each wallet address. INX smart contract is an Ethereum smart-contract written and developed in solidity, and as such, it is designed and programmed to be deployed on the Ethereum public mainnet network. Being deployed on Ethereum public network, make it available to all Ethereum tools, including Etherscan and other block explorers. | |
| 5. | Transfer. INX Tokens may be transferred only among Ethereum wallets included in the Whitelist Database. Transfers of INX Tokens will be executed by the INX Token smart contract under conditional permission that the wallet addresses of both the sender and receiver of INX Tokens are listed on the Whitelist Database. The INX Token smart contract will verify that both the sender and the receiver wallet addresses are included in the Whitelist Database prior to approving or rejecting the transfer. If either the sender or receiver wallet address is not listed in the Whitelist Database, the smart contract will reject the transfer and the INX Token Distributed Ledger will not be updated. | |
| 6. | The INX Token smart contract incorporates a lock function, which restricts the transfer of INX Tokens to or from a specified digital wallet address for a specified time. Once the lock function is activated, INX Tokens cannot be transferred from the locked address until the lock-up period has elapsed. |
C:
2
Main Functions
The following table covers the main (not all) functions of the smart contract.
| Function | Description | Ref | Tested |
| transfer | Transfer (ERC20) funds(inx) from one address to another. - Need to have balance - Value (amount) should not be locked - Validate should pass (0) on proxy contract (external and upgradable validation) |
InxToken.sol | Yes |
| balance Of | Check the balance of an address (ERC20) and returns the value | InxToken.sol | Yes |
| update Inx Service | Updating the address of the proxy contract | InxToken.sol | Yes |
| Constructor (inx token) | Should receive parameter of the initial address of the proxy validation | InxToken.sol | Yes |
| lock | Lock and amount and set its release time (EPOCH) for a specified address | Timelock (InxToken.sol) | Yes |
| release | Immediately release amount for a specified address | Timelock (InxToken.sol) | Yes |
| check None Lock Amount | This function receives an address and an amount (usually the value for transfer) and checks if the amount is locked. If the return value is equal or greater to the amount that was sent, then the whole amount is NOT LOCKED and can be transferred. If the returned value is 0, that means that the WHOLE AMOUNT IS LOCKED and cannot be transferred. |
Timelock (InxToken.sol) | Yes |
C:
3
| check Lockup | Receives address and return the locking status as an array of 2 elements, release time (EPOCH) and amount. If both are 0, then there is no locked amount for this address | Timelock (InxToken.sol) | Yes |
| set White List | Enable owner to set whitelisted status (bool) for an address. A whitelisted address is a struct of boolean (the status) and a string (data). For whitelisting an address the value should be set to true. If the status is changing, the whitelisting should be set to false. | Whitelisting (InxToken.sol) |
Yes |
| is WhiteListed | Returns (bool) the whitelisting status of an address | Whitelisting (InxToken.sol) |
Yes |
| get WhiteList Data | Returns the data (string) of the whitelisted address. | Whitelisting (InxToken.sol) |
Yes |
| check WhiteList Status | Checks the whitelist status of an address | Whitelisting (InxToken.sol) |
Yes |
| get WhiteList Data | Get the data that is set with a whitelist address | Whitelisting | Yes |
| increase Approval | Increase an approved amount to spent. | InxToken | Yes |
| decrease Approval | Decrease approval amount to spent. | InxToken | Yes |
| add Whitelister | Adds an address that is approved for whitelisting other addresses | InxToken | Yes |
| remove Whitelister | Removes an address from the addresses that are approved for whitelisting | InxToken | Yes |
4
| This ‘F-1’ Filing | Date | Other Filings | ||
|---|---|---|---|---|
 | ||||
| Filed on: | 8/19/19 | None on these Dates | ||
| 7/7/19 | ||||
| List all Filings | ||||