The two test networks move at different speeds. Zeronet is much faster than alphanet. This makes a difference in how quickly you can test different scenarios like baking.
In zeronet, each cycle is 128 blocks, and each block has a target time of 20 seconds. So, each cycle should complete in roughly 42.66 minutes, although they may take longer if bakers miss ...
Unfortunately there is no way to directly query just the delegator's reward from TzScan API.
But you can easily use this API call with some extra calculations:
//This is what the baker got
var total_reward = rewards + extra_rewards - losses;
//This is the delegator's share in the staking balance
var share = balance / staking_balance;
//This is the ...
TzScan has a service for that, but only for the current value:
You are sending your query to the wrong address - it should be (note you are missing "chain/main/"):
I recommend using the https version too. I have successfully queried this endpoint with a smart contract of my own and verified the response:
The current protocol does not keep track of a tally of all tez on the network. It would be a good idea to do so, as it permits computing proportional reward, it can serve as a canari against money printing bugs, and it can be used to refine the governance model.
Since the protocol doesn't keep track of it, there's no node RPC that will give you that ...
Alphanet is the test network for tezos users and developers on the chain.
It runs the exact code of mainnet. It only differs by a few constants to run faster. Currently: time_between_block/2, blocks_per_cycle/2, blocks_per_voting_period/4, ... This is also meant to enforce Do not hardwire constants in your code, they may change! :-)
Zeronet is the test ...
I think this will help you find what you're looking for. https://tzstats.com/docs/api/index.html#introduction. I've searched this resource and found numerous endpoints related to delegates, rewards, account hashes, delegation, etc.
EDIT: Yesterday, they've also announced plans to go open-source. https://tzstats.com/blog/next-gen-blockchain-indexing-for-...
You can use the operations endpoint, filtering for transactions:
Obviously swap address for the address in question. You can retreive the amount, destination, source, fee, gas limit, storage limit, if the tx was internal and also if the tx failed or not.
Here is my attempt to explain why it is not surprising that we would see many more double bakes than endorsements:
Under very nice conditions, with a deterministic signature scheme (like ed25519), you will not double endorse. Even if you fail to protect against double endorsements, if you sign endorsements for the same block twice, they are the very same ...
This is how delegator rewards work - when you are looking at the delegator rewards for a given cycle (e.g. cycle 79), the balance displayed is that from the snapshot, which occurred 7 cycles prior. This is because that is the balance used when calculating the bakers stake which produced the rewards (so it makes it easier for bakers to calculate % rewards of ...
This request is using the balance updates that we have disabled on alphanet.
I would recommend to use the node rpc:
But this also gives 0 so your balance is actually of 0.
For generating tz1 address you don't need node.
Moreover, you don't need internet connection for generating address)
You need only some library such as eztz, sotez or ConseilJS
You can find address generation example (for eztz) here
The original TzScan OS available at https://gitlab.com/tzscan/tzscan does not compile easily for the moment unfortunately. You could ask help there.
Otherwise, you can also try an installer script of TzScan OS, available at https://gitlab.com/tezos-southeast-asia/tzscaninstaller . Note that this uses a fork of TzScan OS, available at https://gitlab.com/...
That should help you (Example TzScan API):
Just put in one of the KT1 adresses and it will show you the total rewards per cycle, for the associated tz1 address.