Memory and Callable Args?

Washington · August 3, 2018, 2:44pm

How large a size can Enigma handle for its callableArgs? Is it limited by a node’s memory?

Aaron · August 3, 2018, 2:46pm

The size is a little less than 32kb~ which is the max size of an Ethereum transaction.
See Geth code:

ethereum/go-ethereum/blob/52b1d0945774336a1c2164f873df3c0a72cacaee/core/tx_pool.go#L555


		}
		if queued := pool.queue[addr]; queued != nil {
			txs[addr] = append(txs[addr], queued.Flatten()...)
		}
	}
	return txs
}


// validateTx checks whether a transaction is valid according to the consensus
// rules and adheres to some heuristic limits of the local node (price and size).
func (pool *TxPool) validateTx(tx *types.Transaction, local bool) error {
	// Heuristic limit, reject transactions over 32KB to prevent DOS attacks
	if tx.Size() > 32*1024 {
		return ErrOversizedData
	}
	// Transactions can't be negative. This may never happen using RLP decoded
	// transactions but may occur if you create a transaction using the RPC.
	if tx.Value().Sign() < 0 {
		return ErrNegativeValue
	}
	// Ensure the transaction doesn't exceed the current block limit gas.

and this Q&A:

Topic		Replies	Views
How should callableArgs in compute() of the Enigma contract be formatted? Secret Contracts and Secret Apps	3	649	July 26, 2018
What is the best way for importing a large data set into secret state? Developer Help	3	560	January 30, 2020
Walkthrough Question Developer Help	3	920	September 17, 2018
Reading state on Ethereum contract Developer Help	18	1860	September 6, 2019
Gas Price compared to ethereum Secret Contracts and Secret Apps	1	466	June 12, 2021

Memory and Callable Args?

Related Topics