The ropsten gasLimit remains at around 4.7million.

However other chains have much higher limits now:
mainnet: ~8
kovan: ~7
rinkeby: ~7.3

Can we have the miners raise the limit?

Most recent blocks are mined by these 2 accounts:
0x00d8ae40d9a06d0e7a2877b62e32eb959afbe16d
0x122932e3159bd5190e0dbcef7ba59a6c041ae9da

Who are these miners?

I was fully synced yesterday but today I didn't manage to connect to any peers. Today I get all kind of errors when I try to connect like "Ethereum handshake failed err=EOF", "getsockopt: connection refused"

TRACE[10-25|10:54:45] New dial task                            task="wait for dial hist expire (13.063720892s)"
TRACE[10-25|10:54:45] Starting protocol eth/63                 id=6ce05930c72abc63 conn=staticdial
DEBUG[10-25|10:54:45] Ethereum peer connected                  id=6ce05930c72abc63 conn=staticdial name=Parity/v1.8.0-unstable-9196c72-20170918/x86_64-linux-gnu/rustc1.20.0
DEBUG[10-25|10:54:45] Ethereum handshake failed                id=6ce05930c72abc63 conn=staticdial err=EOF
DEBUG[10-25|10:54:45] Removing p2p peer                        id=6ce05930c72abc63 conn=staticdial duration=1.907ms   peers=0 req=false err=EOF
TRACE[10-25|10:54:58] Dial task done                           task="wait for dial hist expire (13.063720892s)"
TRACE[10-25|10:54:58] New dial task                            task="staticdial 20c9ad97c081d633 52.169.14.227:30303"
TRACE[10-25|10:54:58] Dial error                               task="staticdial 20c9ad97c081d633 52.169.14.227:30303" err="dial tcp 52.169.14.227:30303: getsockopt: connection
refused"
DEBUG[10-25|10:54:58] Can't resolve node                       id=20c9ad97c081d633 err="discovery is disabled"

propose berlin hf block 9_812_189 (feb 23, 2021, 12pm utc)

I'm running:

• Version: Initially 1.7.2, now 1.7.6
• OS: Windows 10
• Installed from exe

I've been having trouble trying to complete an initial sync for the last week. Each time I try, it completes the snapshot download, and then starts downloading blocks but inevitably gets stuck. I started trying earlier this week on v1.7.2 and am still getting the same issue on 1.7.6. I've tried the troubleshooting instructions for ropsten here and connecting to the specified peers doesn't change the outcome.

Here's an example run from today:

./parity --chain ropsten --reserved-peers ropstenpeers.txt --reserved-only

2017-10-14 20:31:40 UTC Starting Parity/v1.7.6-stable-1953533-20171013/x86_64-windows-msvc/rustc1.20.0

The snapshots download, blocks start syncing, then it stalls at 599252.

2017-10-14 21:20:45 UTC Syncing  #599252 6f98…1552     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed   #599172    1/25 p
eers     74 KiB chain   81 MiB db  0 bytes queue    2 MiB sync  RPC:  0 conn,  0 req/s,   0 µs
2017-10-14 21:20:56 UTC Syncing  #599252 6f98…1552     0 blk/s    0 tx/s   0 Mgas/s      0+    0 Qed   #599172    1/25 p
eers     74 KiB chain   81 MiB db  0 bytes queue    2 MiB sync  RPC:  0 conn,  0 req/s,   0 µs

Any suggestions on what I can try next?

README.md here says:

admin.addPeer('enode://6ce05930c72abc632c58e2e4324f7c7ea478cec0ed4fa2528982cf34483094e9cbc9216e7aa349691242576d552a2a56aaeae426c5303ded677ce455ba1acd9d@13.84.180.240:30303')

A member of the geth project at ethereum/go-ethereum#14699 (comment) says:

ethereum/go-ethereum#14699 (comment)

This information conflicts

What's this all about? https://ropsten.etherscan.io/address/0xff2b5d4114190bb6447dbae098096fd274029535

Etherscan says last transaction was 2 days 14 hours ago. https://ropsten.etherscan.io/address/0x687422eea2cb73b5d3e242ba5456b782919afc85

I tried the faucet yesterday and it hasn't worked although my request was queued and I received the transaction hash on the webpage. This is not a problem with ropsten as the Metamask faucet (https://faucet.metamask.io/) has been working up until to a minute ago.

I'm sorry I am not actually the one synching so I have no data for you, but I am cross posting from reddit:
https://www.reddit.com/r/ethereum/comments/63vd1l/these_ropsten_revived_instructions_do_not_seem_to/

I use the following command to run geth with testnet, as per the docs it finishes syncing and able to show the balance properly. But, when I am trying to find the transaction by hash, it returns null.

sudo /usr/bin/geth --testnet --verbosity 3 --rpc  --light --rpcaddr=0.0.0.0 --rpcport=8545 --rpcapi eth,personal,net,web3,db

The last line synced shows,

INFO [02-28|18:22:30] Imported new block headers               count=2 elapsed=5.514ms   number=2742610 hash=5fc97f…b0dc77 ignored=0

The following returns null

curl -X POST --data '{"jsonrpc":"2.0","method":"eth_getTransactionByHash","params":["MY_TX_HASH_HERE"],"id":1}' http://127.0.0.1  -H "Content-Type: application/json"

It returns with,

{"jsonrpc":"2.0","id":1,"result":null}

Any suggestions?

I am having some syncing problems. I add Ropsten nodes manually using the list provided on https://www.ethernodes.org/network/2/nodes. But some of them are giving me the error "Genesis block mismatch".

How is that possible if I am starting my sync from zero?

$ rm -rf ~/.ethereum
$ geth --testnet --fast --cache 2048 --nodiscover --verbosity 4 console
> admin.addPeer('enode://5e5f2bd936397cd6c5774184278e342d5e48372d0341dc577c36adc4e86acc696ef04836b5b23487cce09ed2644094f5e768a8b14b245ec2be9f20780e4cb7e1@34.245.109.226:30303')
true
> DEBUG[08-21|15:43:42.833] Adding p2p peer                          name=Parity/v1.10.9-stabl... addr=34.245.109.226:30303 peers=1
DEBUG[08-21|15:43:42.834] Ethereum peer connected                  id=5e5f2bd936397cd6 conn=staticdial name=Parity/v1.10.9-stable-23a9eef-20180707/x86_64-linux-gnu/rustc1.27.0
DEBUG[08-21|15:43:42.881] Ethereum handshake failed                id=5e5f2bd936397cd6 conn=staticdial err="Genesis block mismatch - 0cd786a2425d16f1 (!= 41941023680923e0)"
DEBUG[08-21|15:43:42.882] Removing p2p peer                        id=5e5f2bd936397cd6 conn=staticdial duration=49.160ms peers=0 req=true err="disconnect requested"
DEBUG[08-21|15:43:50.655] Recalculated downloader QoS values       rtt=20s confidence=1.000 ttl=1m0s

I am using the node https://www.ethernodes.org/node/5e5f2bd936397cd6c5774184278e342d5e48372d0341dc577c36adc4e86acc696ef04836b5b23487cce09ed2644094f5e768a8b14b245ec2be9f20780e4cb7e1

I followed the github's instructions of geth --testnet removedb

then ran

geth --rpc --rpcapi eth,net,web3,personal --testnet --syncmode "fast" console --cache=1024

then manually added the bootnodes according to the github

I still have 0 from admin.peers, 0 for eth.blockNumber and eth.syncing is false.

How do I sync? How long will this take? I hear from 1 person on the Stack Exchange that it can take a week (!)

..

Something's wrong today with Ropsten. Please see e.g. these issue comments:

• raiden-network/raiden#1058 (comment) first realization
• raiden-network/raiden#1058 (comment) four comments
• raiden-network/raiden#1061 (comment) bottom: "... mentioned transaction a68... was visible on etherscan, but disappeared again after ~30 minutes."

Thanks a lot.

Hi,

I am facing an issue in Open-attestation when I am using the Ropsten network.

Here is the link to that issue. Open-Attestation/open-attestation-cli#127

This is my transaction link - https://ropsten.etherscan.io/tx/0x30e0904520d683dc5face3965641fc96bb2b21be3bebac185861641f2e82d2b8

Please advise me. Also, let me know how much time it will take.

I have tried both of these for pools:

//address WETHUSDCPool = 0x88e6A0c2dDD26FEEb64F039a2c41296FcB3f5640;
from https://etherscan.io/address/0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640#readContract -- this looks like the right pool from searching

  address WETHUSDCPool = 0x8ad599c3A0ff1De082011EFDDc58f1908eb6e6D8; //?? linked from uniswap
from https://info.uniswap.org/#/pools/0x8ad599c3a0ff1de082011efddc58f1908eb6e6d -- this one I get from UNISWAP

I always get an error consulting the Uniswap V3 Oracle Library with these pools, it reverts which it can do if there are no reserves.

What is the correct WETH-USDC Pool? Thank you!!

I am trying to deploy a simple test contract with Parity, but for one hour and still see the message "Will deploy a contract". Here is my contract, can anybody else deploy it? :

pragma solidity ^0.4.24;

contract Test2 {
    address public bank;
    address public customer;
    address public producer;
    bytes32 public productName;

    struct Box {
        uint size;
    }
    Box public box;

    constructor() public {
        box.size = 3;
        bank = 0xa2079636c495bDbaCfe...;
        customer = 0xDa3E3C7508fB15c...;
        producer = 0xAEE44304beb9063...;
        productName = "0x5761737...";
    }

    function changeBox(uint _change) public {
        box.size = _change;
    }

    function getBox() public returns (uint) {
        return box.size;
    }  
}

My node was running fine during 2 months. Some day, synchronisation stopped and the console showed the messages "Synchronisation failed, dropping peer" and "Ancestor below allowance". The blockNumber was stuck and syncing was false. I let it run during a week, but it didn't move on.

I removed the chaindata and retried to sync from scratch, it did the job, my node synced well. But a few days later it happened again.

It seems it's stuck in this state.

I'm trying to sync with Ropsten testnet via Parity, but the node doesn't start the sync and Parity doesn't find any peer.
I'm running:

• Parity version: 1.8.5

• OS: MacOS High Sierra 10.13

I tried to restart the node and delete the db but it doesn't help. The network on the node is working fine. I tried to connect to Ropsten even in these 2 ways:

• parity --chain ropsten --bootnodes "enode://20c9ad97c081d63397d7b685a412227a40e23c8bdc6688c6f37e97cfbc22d2b4d1db1510d8f61e6a8866ad7f0e17c02b14182d37ea7c3c8b9c2683aeb6b733a1@52.169.14.227:30303,enode://6ce05930c72abc632c58e2e4324f7c7ea478cec0ed4fa2528982cf34483094e9cbc9216e7aa349691242576d552a2a56aaeae426c5303ded677ce455ba1acd9d@13.84.180.240:30303"

• parity --chain ropsten --reserved-peers ropstenpeers.txt --reserved-only

but the result was the same: it can not find any nodes to connect.
I write down the log:

2018-01-09 17:32:59 State DB configuration: fast
2018-01-09 17:32:59 Operating mode: active
2018-01-09 17:32:59 Configured for Ropsten using Ethash engine
2018-01-09 17:33:00 Updated conversion rate to Ξ1 = US$1203.06 (98954010 wei/gas)
2018-01-09 17:33:00 Public node URL: enode://febfbe472af11566f613dbe8f6963c559ddd013054e7096473d4a643f13d2d080a10c5fe02016c8762f12fe57a837c5ced8a50fbe5c78139a734d2d6cc8ed24b@192.168.1.9:30303
2018-01-09 17:33:34 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-01-09 17:34:05 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-01-09 17:34:35 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-01-09 17:35:05 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-01-09 17:35:35 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-01-09 17:36:05 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs
2018-01-09 17:36:35 0/25 peers 8 KiB chain 111 KiB db 0 bytes queue 448 bytes sync RPC: 0 conn, 0 req/s, 0 µs

Kovan works perfect with Parity instead. What's the problem with Ropsten??

Its been over 2 days since I've been syncing. How does the Ropsten Testnet sync end?
What is the way to confirm this?

Also, please guide on what are the next steps for developing applications post the sync, i.e. how can we utilize this sync for development purposes?

Hello for an application of mine I would need a semi-large amount of ropsten ether (50-100). What would be the best way to go about it? The faucet only drips 0.3 eth an hour. Thanks in advance.

curl http://faucet.ropsten.be:3001/donate/0x7....
curl: (7) Failed to connect to faucet.ropsten.be port 3001: Connection refused

http://faucet.ropsten.be:3001/
This site can’t be reached - faucet.ropsten.be refused to connect.

Hi, I'm having problems to connect in the right testnet ropsten chain. Anyone can share some valid nodes? I tried the nodes of ropsten readme (--nodiscover, addNode..) but unsuccessful and even with --testnet only.

VERSION:
1.8.16-stable-477eb093

geth --testnet --rpc --syncmode "full"

geth --testnet attach

eth.syncing
{
currentBlock: 3418706,
highestBlock: 3418716,
knownStates: 0,
pulledStates: 0,
startingBlock: 3418706
}

peers: [{
caps: ["eth/62", "eth/63", "par/1", "par/2", "par/3", "pip/1"],
id: "36af4d9f8785ee1bc3d8c04eb76bbb705a8b08fc044ef4ffb416808ab3680e18c69e0bda10e25b79920d8e582f8ec65918a223d81efc3330565fc899ae5ecdf9",
name: "Parity-Ethereum/v2.0.6-stable-549e202-20180919/x86_64-linux-gnu/rustc1.29.0",
network: {
inbound: false,
localAddress: "172.31.20.196:47694",
remoteAddress: "35.174.48.76:30303",
static: false,
trusted: false
},
protocols: {
eth: {...}
}
}, {
caps: ["eth/62", "eth/63"],
id: "566009e2787aaabe68012dd63bad920a2eb32b0dedea7b0596635fe3e687a1a0971322a436725d7de93c2bf9005499e9cc898c824cdd40ba5d7e579a54afd40c",
name: "Geth/v1.8.16-stable-477eb093/linux-amd64/go1.10.1",
network: {
inbound: false,
localAddress: "172.31.20.196:39256",
remoteAddress: "35.178.193.227:30303",
static: false,
trusted: false
},
protocols: {
eth: {...}
}
}, {
caps: ["eth/63"],
id: "744316f39e9cb1e5e7013e802731d1e9362a51f6e1030781953b98aae088ce0651f0add5954516c519758a813e705bed127fa933c0d3c0ab970e8ccfab5a2706",
name: "Geth/v1.8.16-stable-477eb093/linux-amd64/go1.10",
network: {
inbound: false,
localAddress: "172.31.20.196:39522",
remoteAddress: "47.75.156.101:30303",
static: false,
trusted: false
},
protocols: {
eth: {...}
}
}],

[3313]: WARN [10-08|12:35:41.551] Ancestor below allowance peer=7ab83cadce8b5f82 number=3328706 hash=000000…000000 allowance=3328706
[3313]: WARN [10-08|12:35:41.551] Synchronisation failed, dropping peer peer=7ab83cadce8b5f82 err="retrieved ancestor is invalid"
[3313]: INFO [10-08|13:02:21.854] Regenerated local transaction journal transactions=0 accounts=0
[3313]: WARN [10-08|13:13:14.812] Synchronisation failed, dropping peer peer=865a63255b3bb680 err="action from bad peer ignored"

After the recent Ropsten fork I can not synchronize to the normal Ropsten network.
I am using parity 1.10.6
I tried warp sync and --no-warp sync. Neither helped. I end up on the chain with best block ~3,069,000, while the actual latest block now is ~3410246.
Are there any stable Ropsten enodes to connect to in order to sync to normal Ropsten? How would one avoid such forked networks generally?