navcoin / development Goto Github PK

https://testnet.navexplorer.com/ is not working yet

https://www.navexplorer.com/address/NPfWgKJAC3AAF5E49LE3RdZE6jUY2bZLKw <- this address shows balance but the transaction history shows it should have 0 balance

Today I published @aguycalled/bitcore-p2p which adds support for the P2P protocol from JavaScript.

This module allows light wallets or JS apps to connect to the Navcoin network and receive candidate transactions for aggregation or fetch orders from the on chain order book.

Browsers and therefor progressive web apps do not have access to socket based communications. Using web sockets is the only option to interact with the network.

We need:

• navcoin/navcoin-core#927
• navcoin/navcoin-js#17

• Migrating navexplorer to hetzner (navcoin/navexplorer-frontend#110)
• Migrating navpool to hetzner navcoin/navexplorer-frontend#112
• Enable staking on the navexplorer node for the navpool stakers
• Remove voting ui from navpool (https://github.com/NavPool/navpool.com/issues/13)
• Finish the search by cold staking address pr (navcoin/navexplorer-frontend#106)

@sakdeniz requested to add the option to the RPC command resolvename to return a name's subdomain.

• Required changes in navcoin-core
• Required changes in electrumx
• navcoin/navcoin-js#7
• navcoin/infrastructure#1
• Testing and confirmation from @sakdeniz
• Update mainnet infrastructure

This is a task meant for collecting ideas, tasks or requirements to get the NavExplorer to the next level.
It can be anything to improve the current NavExplorer, or implement new features according to the development of the Navcoin ecosystem.
Issues can be created upon the list collected here.

@aguycalled @dantudor @mxaddict

https://www.navexplorer.com/dao/consultation/de5784868886da6d06be201a570c3bc7670fceb5bac97ca65fc5f46d83dbf26c <- explorer does not count consultation support votes

We need to implement the ability to prove ownership of specific private NFTs.

An NFT owner should be able to create a cryptographic proof which can be verified to confirm its correctness.

A valid cryptographic proof could be a message "OWNERSHIP_PROOF_NFT"||OUTPOINT||TOKENID signed with the NFT's spending key where:

• "OWNERSHIP_PROOF_NFT" is a string literal
• || is the concatenation operator
• OUTPOINT is the current UTXO of the NFT we are proving ownership of as a string in the format txid:vout
• TOKENID is the serialisation of the NFT Identifier as per the Navcoin-core rules (32 bytes uint256 hash concatenated with uint64 integer)

A validator would receive this proof together with the TOKENID and would check the latest OUTPOINT of the NFT from a full node. Then will verify the signature with the spending key of that outpoint to confirm or reject the ownership claim.

Changes needed in navcoin-core:

• navcoin/navcoin-core#919
• navcoin/navcoin-core#920

Changes needed in electrumx:

• Support for the RPC changes related to showing last UTXO of an NFT

Changes needed in navcoin-js:

• navcoin/navcoin-js#15
• navcoin/navcoin-js#16

We need to sync aguycalled/ledger-app-nav with upstream in order to be compatible with latest Ledger firmware and get the app reviewed by their team.

• #3
• list 2
• list 3