SIG’s Ethereum example burns a shielded claim before payout, while restoring it after failure requires an attested outcome.

Withdrawals from SIG Network’s experimental Ethereum vault require its signing network, even though the underlying assets stay on Ethereum. The example illustrates the withdrawal dependency in Midnight’s Nightmode privacy plan: users burn a shielded claim before the external transfer is signed, and failed-transfer recovery also needs an attested response.

Charles Hoskinson’s @IOHK_Charles account welcomed Tron to Midnight on Oct. 21. SIG’s roadmap targets Tron for December 2026, while its listed Ethereum integration is on the stagenet test network.

SIG describes its service as giving a Midnight contract an ordinary Ethereum account. A threshold of signers produces the Ethereum signature when the contract requests it. SIG says the signers are independent and that no single signer can act alone.

In this educational and experimental application, the underlying ERC20 tokens sit in the vault’s EVM account. On Midnight, users hold shielded vault tokens representing their claims on that pool. Native assets staying on Ethereum therefore answers where the assets are recorded; it does not, by itself, answer who can make them move.

The distinction also explains the burn. Starting a withdrawal destroys the shielded claim being redeemed, rather than destroying the underlying ERC20. A successful external payment finishes the redemption. If the payment receives one of the documented failure outcomes, the application can restore the claim.

The withdrawal walkthrough treats the holder’s coin spend as authorization. The holder supplies a shielded vault coin matching the token and exact withdrawal amount, then chooses a destination address.

Source link