hey

hey

does the blockchain have to be fully synced before creating a testnet

let me rephrase that. after starting the daemon, does it have to be fully synced before i can run a testnet

No.

You can run an offline testnet with whatever chain you like. I often start --offline with a not quite synced db, then mine my blocks on top.

okay, so ive set up my testnet and mining blocks with my set difficulty. However, it is not asking me how much of the block reward I want after each block is mined. I feel like i am missing something here

Why would it ask you? Maybe I’m missing something.

well i added the piece of code that forces all miners to take the same coinbase reward again like in version 1.

and in my mind, there would be a prompt that would ask the miner how much of the coinbase reward they want up to R which is the max reward. I am probably going about it wrong

Why the hell would you want to ask "do you want to claim only part of the reward, which will make your block invalid ?" ?

thats the point. to prove that it can be made invalid if i say i want only a piece of it.

Then you want to make a test, not have tests embedded in day to day binaries.

See core tests. They're hard to get a hang of though, so...

okay. but question. i was looking at the codebase and i thought this was the test which led to me asking if there was a prompt to begin with

MDEBUG is a logging macro, not an input one.

ohhh got it

can you compile two different versions of monero and run two different testnets on one machine?

Yes. Use different data directories and ports.

is it fine if it both versions bind to the same ip? If i run the daemon for both versions on the same machine, figured they shouldn't bind the same ip?

They can. Just use a different port.

so how do you reference each version to a testnet? I have both testnets running but I want one to run one version and another to run the other version. I compiled both and there were no issues.

You can compile different commits in separate build directories and use corresponding executable when need specific version.