From 81f85ec6b222f4aac3437c80130b8a62c151a873 Mon Sep 17 00:00:00 2001
From: Flouse <1297478+Flouse@users.noreply.github.com>
Date: Thu, 14 Sep 2023 23:06:46 +0800
Subject: [PATCH] test: send non eip155 tx to Axon (#299)

non-EIP-155 transactions are mainly to support [EIP-1820](https://eips.ethereum.org/EIPS/eip-1820). Many projects use this method to support multi-chain contracts using the same address.

> [EIP-155](https://eips.ethereum.org/EIPS/eip-155): The currently existing signature scheme using v = 27 and v = 28 remains valid and continues to operate under the same rules as it did previously.
---
 contracts/test/nonEip155.js | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/contracts/test/nonEip155.js b/contracts/test/nonEip155.js
index d9fbf5ec..68b8aa74 100644
--- a/contracts/test/nonEip155.js
+++ b/contracts/test/nonEip155.js
@@ -8,12 +8,13 @@ const { getTxReceipt } = require("../utils/receipt");
 
 const { ethers } = hardhat;
 
+// non-EIP-155 transactions are mainly to support EIP-1820. Many projects use
+// this method to support multi-chain contracts using the same address.
+//
+// EIP-155: The currently existing signature scheme using v = 27 and v = 28
+// remains valid and continues to operate under the same rules as it did
+// previously.
 describe("Non eip155 tx", function () {
-  //FIXME
-  if (isAxon()) {
-    return;
-  }
-
   it("Send non eip155 tx", async function () {
     const [owner] = await ethers.getSigners();