search

reddcoin-project / reddsight-api

The official Reddcoin blockchain API in Javascript
7 stars 8 forks source link

Reddsight socket.io issue with stake transactions #2

Closed skolmer closed 9 years ago

skolmer commented 9 years ago

I'm currently working on a tool that is listening for new transactions via socket.io The code looks like this:

socket.emit('subscribe', 'RZCRLMnDAhC91zaSLkJoPRbSHGuLJimZ7u'); socket.on('RZCRLMnDAhC91zaSLkJoPRbSHGuLJimZ7u', function(tx) { ... });

This is working fine for normal transactions, but if a new stake transaction happens the event is not getting fired.

I found a wallet that is staking quite often: http://live.reddcoin.com/address/Ra7aAgKuG2UkW1MJuquMLVJUzirguD6M9j If you watch this address you will notice that reddsight is not playing the typical sound or updating the transaction history when a new stake occurs.

Can you confirm this issue or am I doing something wrong?

laudney commented 9 years ago

This is working as expected. Coinstake transactions are not broadcast to the network and only exist in valid PoSV blocks. As a result, you shouldn't expect coinstake transactions to trigger. Instead you should listen for event on new blocks and dig into those block to find coinstake transactions.

skolmer commented 9 years ago

I understand that but from a user perspective I would expect that live.reddcoin.com will show me a coinstaking transaction like any other transaction in real-time. I mean if I send some coins to an address, redsight is immediately playing a sound and showing the transaction in the transaction list. If a coinstake transaction occurs nothing happens and the transaction is only shown if I refresh the page manually.

From a developer perspective I'm trying to keep api calls to a minimum to avoid unnecessary traffic on mobile devices. If I understand you right the current way would be to request full block data every time a block is broadcasted and look for the right address and coinstake information.

Another channel that is broadcasting coinstake transactions for specific addresses would be therefore a welcome feature. This might be a feature request and not a bug but could you put it on the todo list even if it takes months to be ready? If it doesn't have a high priority that's ok.