Migration to Apothem not working #390
Comments
|
Could you please share your codes? So we can make tests. |
|
there it is click here
<https://github.com/SumerRana/apothemFailureTest/tree/master> or visit
https://github.com/SumerRana/apothemFailureTest/tree/master
…On Fri, Jan 12, 2024 at 8:59 AM Daniel Liu ***@***.***> wrote:
Could you please share your codes? So we can make tests.
—
Reply to this email directly, view it on GitHub
<#390 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7EDGFKVPXTTU3AL6Z6XJZTYOCUY7AVCNFSM6AAAAABBWNJKNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBYGM3TMNRYGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
any updates?
…On Sun, Jan 14, 2024 at 2:06 PM Sumer Rana ***@***.***> wrote:
there it is click here
<https://github.com/SumerRana/apothemFailureTest/tree/master> or visit
https://github.com/SumerRana/apothemFailureTest/tree/master
On Fri, Jan 12, 2024 at 8:59 AM Daniel Liu ***@***.***>
wrote:
> Could you please share your codes? So we can make tests.
>
> —
> Reply to this email directly, view it on GitHub
> <#390 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A7EDGFKVPXTTU3AL6Z6XJZTYOCUY7AVCNFSM6AAAAABBWNJKNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBYGM3TMNRYGI>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
I have shared the code, please check |
|
Sorry, it will take time to resolve this issue. We will keep you updated on the progress. |
|
yeah, I'll build on another network,
where having a working network is a high priority task
Xinfin is a disappointment
…On Tue, Feb 6, 2024, 7:33 AM Daniel Liu ***@***.***> wrote:
Sorry, the whole team is working on higher priority tasks now.
—
Reply to this email directly, view it on GitHub
<#390 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7EDGFLLNBT7VRNV3FENTM3YSGFOZAVCNFSM6AAAAABBWNJKNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRYGY2DQMRUGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Please change |
|
This issue was just fixed. Both of RPC node |
|
Awesome, thanks for the update!
…On Wed, Feb 7, 2024, 10:18 AM Daniel Liu ***@***.***> wrote:
This issue was just fixed. Both of RPC node erpc.apothem.network and
earpc.apothem.network works fine now.
—
Reply to this email directly, view it on GitHub
<#390 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7EDGFJCGT4NUKH5US2SDQ3YSMBSBAVCNFSM6AAAAABBWNJKNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZRGI3TMMZTGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
closed as the problem is solved. |
|
its back again
[image: image.png]
…On Thu, Feb 8, 2024 at 12:48 PM Daniel Liu ***@***.***> wrote:
closed as the problem is solved.
—
Reply to this email directly, view it on GitHub
<#390 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7EDGFJUKY7T2X4WL7VA3ZDYSR33DAVCNFSM6AAAAABBWNJKNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZTGQ4DMMJSGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I tested your project just now, but found no problem: |
|
thanks for reply,
if it is working for you then there must be a problem in my setup
will check it
thank you
…On Thu, Feb 22, 2024 at 4:24 PM Daniel Liu ***@***.***> wrote:
I tested your project just now, but found no problem:
npx truffle migrate --network apothem
Need to install the following packages:
***@***.***
Ok to proceed? (y) y
npm WARN deprecated ***@***.***: this library is no longer supported
npm WARN deprecated ***@***.***: testrpc has been renamed to ganache-cli, please use this package from now on.
npm WARN deprecated ***@***.***: The `apollo-server-types` package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023 and October 22nd 2024, respectively). This package's functionality is now found in the ***@***.***/server` package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details.
npm WARN deprecated ***@***.***: This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that.
npm WARN deprecated ***@***.***: The `apollo-server-plugin-base` package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023 and October 22nd 2024, respectively). This package's functionality is now found in the ***@***.***/server` package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details.
npm WARN deprecated ***@***.***: The `apollo-server-errors` package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023 and October 22nd 2024, respectively). This package's functionality is now found in the ***@***.***/server` package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details.
npm WARN deprecated ***@***.***: The `apollo-datasource` package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023 and October 22nd 2024, respectively). See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details.
npm WARN deprecated ***@***.***: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated ***@***.***: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated ***@***.***: This module has been superseded by the multiformats module
npm WARN deprecated ***@***.***: The `apollo-server-env` package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023 and October 22nd 2024, respectively). This package's functionality is now found in the ***@***.***/utils.fetcher` package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details.
npm WARN deprecated ***@***.***: request has been deprecated, see request/request#3142
npm WARN deprecated ***@***.***: This module has been superseded by the multiformats module
npm WARN deprecated ***@***.***: The `apollo-reporting-protobuf` package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023 and October 22nd 2024, respectively). This package's functionality is now found in the ***@***.***/usage-reporting-protobuf` package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details.
npm WARN deprecated ***@***.***: This module has been superseded by the multiformats module
npm WARN deprecated ***@***.***: This module has been superseded by the multiformats module
npm WARN deprecated ***@***.***: This module has been superseded by the multiformats module
npm WARN deprecated @***@***.***: Please use @ensdomains/ens-contracts
npm WARN deprecated @***@***.***: Please use @ensdomains/ens-contracts
Compiling your contracts...
===========================
✓ Fetching solc version list from solc-bin. Attempt #1
✓ Downloading compiler. Attempt #1.
> Compiling ./contracts/MyToken.sol
> Compiling ./contracts/MyToken2.sol
> Compiling ./contracts/MyToken3.sol
> Compiling ./contracts/MyToken4.sol
> Compiling @openzeppelin/contracts/interfaces/IERC5267.sol
> Compiling @openzeppelin/contracts/token/ERC20/ERC20.sol
> Compiling @openzeppelin/contracts/token/ERC20/IERC20.sol
> Compiling @openzeppelin/contracts/token/ERC20/extensions/ERC20Permit.sol
> Compiling @openzeppelin/contracts/token/ERC20/extensions/IERC20Metadata.sol
> Compiling @openzeppelin/contracts/token/ERC20/extensions/IERC20Permit.sol
> Compiling @openzeppelin/contracts/utils/Context.sol
> Compiling @openzeppelin/contracts/utils/Counters.sol
> Compiling @openzeppelin/contracts/utils/ShortStrings.sol
> Compiling @openzeppelin/contracts/utils/StorageSlot.sol
> Compiling @openzeppelin/contracts/utils/Strings.sol
> Compiling @openzeppelin/contracts/utils/cryptography/ECDSA.sol
> Compiling @openzeppelin/contracts/utils/cryptography/EIP712.sol
> Compiling @openzeppelin/contracts/utils/math/Math.sol
> Compiling @openzeppelin/contracts/utils/math/SignedMath.sol
> Artifacts written to /home/me/apothemFailureTest/build/contracts
> Compiled successfully using:
- solc: 0.8.16+commit.07a7930e.Emscripten.clang
Starting migrations...
======================
> Network name: 'apothem'
> Network id: 51
> Block gas limit: 420000000 (0x1908b100)
1_token_migration.js
====================
Deploying 'MyToken'
-------------------
> transaction hash: 0x04433f973d8b45f69580a4912e56df207a58b675c401c30067a8f66da256c3de
> Blocks: 4 Seconds: 10
> contract address: 0x420d7DC21458bbc04D4f07BE1A6b82e61E69dc76
> block number: 60266587
> block timestamp: 1708599056
> account: 0xD4CE02705041F04135f1949Bc835c1Fe0885513c
> balance: 21186.97168560825
> gas used: 2745148 (0x29e33c)
> gas price: 12.5 gwei
> value sent: 0 ETH
> total cost: 0.03431435 ETH
Deploying 'MyToken2'
--------------------
> transaction hash: 0x10ffe38005eebdc8628bdd977600faba901e2410e0a6729213afeb995cdea29e
> Blocks: 4 Seconds: 9
> contract address: 0x71f18cF12E871BA6f6324d087217B0adB356fd2a
> block number: 60266594
> block timestamp: 1708599072
> account: 0xD4CE02705041F04135f1949Bc835c1Fe0885513c
> balance: 21186.93737125825
> gas used: 2745148 (0x29e33c)
> gas price: 12.5 gwei
> value sent: 0 ETH
> total cost: 0.03431435 ETH
Deploying 'MyToken3'
--------------------
> transaction hash: 0x0ae8a35ef41ed105d18630526615879fdc762b8f6891457e3b3e6b15f088489d
> Blocks: 4 Seconds: 9
> contract address: 0x4434a6FE0f233B2D38Faf39483EdaF319c850178
> block number: 60266601
> block timestamp: 1708599089
> account: 0xD4CE02705041F04135f1949Bc835c1Fe0885513c
> balance: 21186.90305690825
> gas used: 2745148 (0x29e33c)
> gas price: 12.5 gwei
> value sent: 0 ETH
> total cost: 0.03431435 ETH
Deploying 'MyToken4'
--------------------
> transaction hash: 0x42c9ef01703eaa94bcf21974462bb62c30c781c28e1e506cce16ec0377d0f398
> Blocks: 4 Seconds: 9
> contract address: 0x802F8e5A3dEfE64BdB84Df45A34ff0c901602031
> block number: 60266608
> block timestamp: 1708599104
> account: 0xD4CE02705041F04135f1949Bc835c1Fe0885513c
> balance: 21186.86874255825
> gas used: 2745148 (0x29e33c)
> gas price: 12.5 gwei
> value sent: 0 ETH
> total cost: 0.03431435 ETH
> Saving artifacts
-------------------------------------
> Total cost: 0.1372574 ETH
Summary
=======
> Total deployments: 4
> Final cost: 0.1372574 ETH
—
Reply to this email directly, view it on GitHub
<#390 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7EDGFK7KVDLCHRPVTCGOTTYU4PVHAVCNFSM6AAAAABBWNJKNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJZGE4TCOBTGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
is apothem network down again?
truffle migrate --network apothem
Compiling your contracts...
Artifacts written to C:\<location>
Compiled successfully using:
- solc: 0.8.16+commit.07a7930e.Emscripten.clang
C:\Users\sumer\OneDrive\Desktop\Workbench\theblockchainland-backend\tokenContracts\node_modules\eth-block-tracker\src\polling.js:51
const newErr = new Error(`PollingBlockTracker - encountered an
error while attempting to update latest block:\n${err.stack}`)
^
Error: PollingBlockTracker - encountered an error while attempting to
update latest block:
undefined
at PollingBlockTracker._performSync
(C:<location>/node_modules\eth-block-tracker\src\polling.js:51:24)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
UnhandledRejections detected
Promise {
<rejected> {
code: -32603,
message: 'Unknown Error: error code: 523',
data: { originalError: {} }
}
} {
code: -32603,
message: 'Unknown Error: error code: 523',
data: { originalError: {} }
}
…On Mon, Feb 26, 2024 at 8:01 AM Daniel Liu ***@***.***> wrote:
Closed #390 <#390> as
completed.
—
Reply to this email directly, view it on GitHub
<#390 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7EDGFIMYYQM2QH77PGZAPDYVPXXHAVCNFSM6AAAAABBWNJKNKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRHEYTIOBZGM3DEMY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
is apothem network down again?
truffle migrate --network apothem
Compiling your contracts...
Artifacts written to C:\<location>
Compiled successfully using:
- solc: 0.8.16+commit.07a7930e.Emscripten.clang
C:\<location>node_modules\eth-block-tracker\src\polling.js:51
const newErr = new Error(`PollingBlockTracker - encountered an
error while attempting to update latest block:\n${err.stack}`)
^
Error: PollingBlockTracker - encountered an error while attempting to
update latest block:
undefined
at PollingBlockTracker._performSync
(C:<location>/node_modules\eth-block-tracker\src\polling.js:51:24)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
UnhandledRejections detected
Promise {
<rejected> {
code: -32603,
message: 'Unknown Error: error code: 523',
data: { originalError: {} }
}
} {
code: -32603,
message: 'Unknown Error: error code: 523',
data: { originalError: {} }
}
…On Mon, Feb 26, 2024 at 8:01 AM Daniel Liu ***@***.***> wrote:
Closed #390 <#390> as
completed.
—
Reply to this email directly, view it on GitHub
<#390 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7EDGFIMYYQM2QH77PGZAPDYVPXXHAVCNFSM6AAAAABBWNJKNKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRHEYTIOBZGM3DEMY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Hi Daniel,
The apothem Network has been extremely unreliable since last 8-10 days,
the team is considering leaving Apothem and moving to Avalanche Fiji or
Celo Alfajores
Please make the network stable for us to keep building on Apothem.
Thank you
…On Mon, Feb 26, 2024 at 8:01 AM Daniel Liu ***@***.***> wrote:
Closed #390 <#390> as
completed.
—
Reply to this email directly, view it on GitHub
<#390 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7EDGFIMYYQM2QH77PGZAPDYVPXXHAVCNFSM6AAAAABBWNJKNKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRHEYTIOBZGM3DEMY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Hi Daniel,
The apothem Network has been extremely unreliable since last 8-10 days,
the team is considering leaving Apothem and moving to Avalanche Fiji or
Celo Alfajores
Please make the network stable for us to keep building on Apothem.
Thank you
…On Sun, Sep 8, 2024 at 7:15 PM Sumer Rana ***@***.***> wrote:
Hi Daniel,
The apothem Network has been extremely unreliable since last 8-10 days,
the team is considering leaving Apothem and moving to Avalanche Fiji or
Celo Alfajores
Please make the network stable for us to keep building on Apothem.
Thank you
On Mon, Feb 26, 2024 at 8:01 AM Daniel Liu ***@***.***>
wrote:
> Closed #390 <#390> as
> completed.
>
> —
> Reply to this email directly, view it on GitHub
> <#390 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A7EDGFIMYYQM2QH77PGZAPDYVPXXHAVCNFSM6AAAAABBWNJKNKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRHEYTIOBZGM3DEMY>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
The network is down again[image: image.png]
…On Wed, Sep 18, 2024 at 9:46 PM Sumer Rana ***@***.***> wrote:
Hi Daniel,
The apothem Network has been extremely unreliable since last 8-10 days,
the team is considering leaving Apothem and moving to Avalanche Fiji or
Celo Alfajores
Please make the network stable for us to keep building on Apothem.
Thank you
On Sun, Sep 8, 2024 at 7:15 PM Sumer Rana ***@***.***> wrote:
> Hi Daniel,
> The apothem Network has been extremely unreliable since last 8-10 days,
> the team is considering leaving Apothem and moving to Avalanche Fiji or
> Celo Alfajores
> Please make the network stable for us to keep building on Apothem.
> Thank you
>
> On Mon, Feb 26, 2024 at 8:01 AM Daniel Liu ***@***.***>
> wrote:
>
>> Closed #390 <#390> as
>> completed.
>>
>> —
>> Reply to this email directly, view it on GitHub
>> <#390 (comment)>,
>> or unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/A7EDGFIMYYQM2QH77PGZAPDYVPXXHAVCNFSM6AAAAABBWNJKNKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRHEYTIOBZGM3DEMY>
>> .
>> You are receiving this because you authored the thread.Message ID:
>> ***@***.***>
>>
>
|
|
Hello @SumerRana, I’ve verified that the Apothem Network is up and running without any issues, as shown in the screenshot below:
Could you kindly share the RPC endpoint you’ve configured in your code along with the specific error you’re encountering? This will help us troubleshoot the issue more effectively. |
|
[image: image.png]
thanks for the prompt reply, this is what we are using
…On Tue, Jan 14, 2025 at 10:51 PM Anil Chinchawale ***@***.***> wrote:
Hello @SumerRana <https://github.com/SumerRana> ,
I can see that Apothem Network is up and running without any issue.
Screenshot.2025-01-14.at.10.50.22.PM.png (view on web)
<https://github.com/user-attachments/assets/e342e3d7-3360-4456-a382-fc847b2d8c39>
Can you help us with rpc that you have configured in your code with error ?
—
Reply to this email directly, view it on GitHub
<#390 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7EDGFLQT7GZYPAYKMIVKMD2KVBQXAVCNFSM6AAAAABBWNJKNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJQGYZDGNBZGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Hey, Can you share steps to reproduce error that you are facing , You can share it here or post over xdc.dev |
|
[image: image.png]
this is what we're getting, same script was running hours ago, contract was
getting deployed with 10 seconds, now its failing after 750 seconds
THERE IS A PROBLEM WITH THE NETWORK.
thank you
…On Tue, Jan 14, 2025 at 10:54 PM Sumer Rana ***@***.***> wrote:
[image: image.png]
thanks for the prompt reply, this is what we are using
On Tue, Jan 14, 2025 at 10:51 PM Anil Chinchawale <
***@***.***> wrote:
> Hello @SumerRana <https://github.com/SumerRana> ,
>
> I can see that Apothem Network is up and running without any issue.
> Screenshot.2025-01-14.at.10.50.22.PM.png (view on web)
> <https://github.com/user-attachments/assets/e342e3d7-3360-4456-a382-fc847b2d8c39>
>
> Can you help us with rpc that you have configured in your code with error
> ?
>
> —
> Reply to this email directly, view it on GitHub
> <#390 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A7EDGFLQT7GZYPAYKMIVKMD2KVBQXAVCNFSM6AAAAABBWNJKNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJQGYZDGNBZGY>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
|
Attachment is not visible as you might sending it from email , I suggest you share script here and error in text. |
|
We have been interacting with at code at this address for 4-5 days now,
never faced a problem,
now it says the code doesn't even exist.
There is indeed a problem with the network
[image: image.png]
…On Tue, Jan 14, 2025 at 11:00 PM Sumer Rana ***@***.***> wrote:
[image: image.png]
this is what we're getting, same script was running hours ago, contract
was getting deployed with 10 seconds, now its failing after 750 seconds
THERE IS A PROBLEM WITH THE NETWORK.
thank you
On Tue, Jan 14, 2025 at 10:54 PM Sumer Rana ***@***.***> wrote:
> [image: image.png]
> thanks for the prompt reply, this is what we are using
>
>
> On Tue, Jan 14, 2025 at 10:51 PM Anil Chinchawale <
> ***@***.***> wrote:
>
>> Hello @SumerRana <https://github.com/SumerRana> ,
>>
>> I can see that Apothem Network is up and running without any issue.
>> Screenshot.2025-01-14.at.10.50.22.PM.png (view on web)
>> <https://github.com/user-attachments/assets/e342e3d7-3360-4456-a382-fc847b2d8c39>
>>
>> Can you help us with rpc that you have configured in your code with
>> error ?
>>
>> —
>> Reply to this email directly, view it on GitHub
>> <#390 (comment)>,
>> or unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/A7EDGFLQT7GZYPAYKMIVKMD2KVBQXAVCNFSM6AAAAABBWNJKNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJQGYZDGNBZGY>
>> .
>> You are receiving this because you were mentioned.Message ID:
>> ***@***.***>
>>
>
|
|
Hello @SumerRana, Could you confirm if the testing was performed using the code available at the following repository? https://github.com/SumerRana/apothemFailureTest Additionally, you can review the XDC Explorer to verify contract interactions for other tokens at this link: Side Note: |
|
@SumerRana Sorry, all of your images can't be displayed on GitHub. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I used truffle and hardhat to deploy smart contracts on the apothem testnet, everything was working fine but suddenly it stopped working a few days ago and has not worked since, the code is working on local ganache and mumbai network, no problems there, but Apothem is not working.
truffle migrate --network apothem
Compiling your contracts...
\tradingContractsSystem\build\contracts
Starting migrations...
1_boss_migration.js
Deploying 'Boss'
*** Deployment Failed ***
"Boss" -- Unknown Error:
<title>500 Internal Server Error</title>500 Internal Server Error
nginx/1.18.0 (Ubuntu) .
Exiting: Review successful transactions manually by checking the transaction hashes above on Etherscan.
Error: *** Deployment Failed ***
"Boss" -- Unknown Error:
<title>500 Internal Server Error</title>500 Internal Server Error
nginx/1.18.0 (Ubuntu) .
Truffle v5.11.5 (core: 5.11.5)
Node v18.19.0
The text was updated successfully, but these errors were encountered: