I am expecting that you already executed npm init at first.
I assume you are using windows? I always develop blockchain related stuff on Ubuntu.
Here is what you need to do on windows to set it up properly.
Step 1: npm install -g --production windows-build-tools
Step 2: npm install -g node-gyp
Now it should work!
If you still have a problem make sure ...
Unless you have a single authority reorganizations are still possible in a PoA.
The authority in turn has to sign and send the block on time to the rest of network. If the next authority fails to receive the block on time it has to produce a new block and propagate it to the network. Until the consensus is resolved some nodes might see different chains.
Is there any public node url there for ETC?
Custom URL: https://classic.blockscout.com 14 or https://ethereumclassic.network
Also, you can advise users to use Nifty wallet Chrome extension (github) with your dApp since it has native support of ETC:
Yes, that's possible. Run the ganache-cli from the terminal that run test ethereum blockchain by default at localhost:8545.
Now deploy your contracts on the ganache.
Now in the node.js application import web3 and with web3 object connect to the contract via contract address- web3.eth.contract(ABI).at(contractAddress), this will give the connection object in ...
It seems the block gas limit in your network has fallen bellow 8M, and your transaction gas is above 8M. Transactions with gas above the network gas limit are not processed until the limit rises.
You can check gasLimit of the latest block in your network executing eth.getBlock('latest') from geth's console.
Send transaction with less gas ...
This is basically down to the interpretation of your input data as bytes or as a string. A good way to test this is using web3 in a browser (eg just visit the remix site and there's a console window you can use. This shows the following: