### Summary branches virtual counters

ForkId 5:
- zkevm-testvectors: [feature/forkid-5-vcounters](https://github.com/0xPolygonHermez/zkevm-testvectors/pull/211)
- zkevm-commonjs: [feature/forkid-5-vcounters](https://github.com/0xPolygonHermez/zkevm-commonjs/pull/112)
- zkevm-rom: [feature/forkid-5-vcounters](https://github.com/0xPolygonHermez/zkevm-rom/pull/309)

Etrog:Still WIP -> waiting to completely finish rom

### Testing full tracer
This services, tests that it is posible to recreate the same exact geth response of a debug_trace call from the full tracer response. We have two services:
- Test against proverjs full tracer response
- Test against executor full tracer response
<br>

You can find the services at `/tools/full-tracer-tests` from `zkevm-proverjs` git repository.
- There is a readme
- You need to have test-vectors from forkid 5 at same folder
- `node --max-old-space-size=16000 full-tracer-tests.js`
- In case testing agains executor, set the executor's endpoint directly at the code

const client = new ExecutorService('51.210.116.237:50071', grpc.credentials.createInsecure(), { 'grpc.max_receive_message_length': 91837108 });
const dbClient = new HashDBService('51.210.116.237:50061', grpc.credentials.createInsecure());

- If is the first time this test is run, it will take longer because it will emulate the geth environment in a docker and will store geth response localy. For next run, the response will be obtained from the stored file.

!! This service is still in WIP until full tracer is completely defined, some errors may appear