Interesting project!. Some questions...

[danesposi]

Hey Alongside team!.

According to the whitepaper located in your webpage and the code here available, an authorized role known as merchant is responsible for requesting index token mints:

amkt-contracts/src/factory/Factory.sol

Lines 129 to 133 in bcefceb

	function addMintRequest(
	uint256 amount,
	string memory txid,
	string memory depositAddress
	) external override onlyMerchant whenNotPaused returns (uint256) {

this request is then hashed and stored as a key to access its nonce, which is the last index of the mintRequest array, and then pushed to such array:

amkt-contracts/src/factory/Factory.sol

Lines 140 to 153 in bcefceb

	Request memory request = Request({
	requester: msg.sender,
	amount: amount,
	depositAddress: depositAddress,
	txid: txid,
	nonce: nonce,
	timestamp: timestamp,
	status: RequestStatus.PENDING
	});
	bytes32 requestHash = calcRequestHash(request);
	mintRequestNonce[requestHash] = nonce;
	mintRequests.push(request);

Later on, another authorized role known as issuer is now responsible for canceling or confirming such request. If such request is confirmed, then the requested amount of index tokens are issued to the requesterer specified by the merchant.

I'm genuinely intrigued about how can we publicly verify that the corresponding underlying assets were deposited to the protocol (depositing 25 different assets doesn't sound like an easy task at all) and no false values are being reported?.

Kind regards.

Andro Team.