Topic: [ANN]🌀 Blur Network(BLUR) 🌀 | PoW Cryptonight-Dynamic | CPU/Solo Mining | DPoW - page 3. (Read 41322 times)

Explorer is up now. Yes, no more trading volume in altilly, you might get delisted if this will continue. Will try to mine this coin and let's see if I can still get something. Never used that Txbit before but you have better price on that exchange than altilly and of course there is active trading.

(outdated info removed)

Sorry! Explorer was down for a few hours. It is back up now. 99% of BLUR’s trading volume  is on Txbit.io. I would prefer that some of the volume move over to Altilly as well, so please place an offer there if you want! However, you may have better luck on Txbit.

Why my wallet not sync?

blurd.exe --add-priority-node=66.70.188.178:52541 --add-priority-node=66.70.189.131:52541 --add-priority-node=66.70.189.183:52541 --p2p-bind-port=52541 --rpc-bind-port=52542 --rpc-bind-ip=127.0.0.1

explorer is working here?

No more trading volume in altilly dev? What is happening? But there is a long list of buy and sell orders though. I checked this to see if I can cpu mine this coin because the price is not bad as compared to other cpu mineable coin. However, I want to check the current difficulty but your explorer is not up :

You must be mistaken. This is the first project I’ve created. Planning on it being the only one as well.


It’s a part of why we are choosing to confine things to a single enclosed ecosystem. I feel that a lot of what goes on with CryptoNote clones is bad for crypto in general. We don’t need more copy coins. I think that if one is going to do so, there should be an expectation of it being made known that the developer has multiple projects... and I think that they should be confined to the same ecosystem, in that event. But this is just my personal ethical compass

UPDATE: DPoW development on Blur is nearing completion.

You will find, below, an update on the progress so far:

1.) Code for keeping track of notary node signatures (sig_count), and an index for keeping track of which nodes have signed the pending_tx (signers_index), is complete and functional.

2.) The code to start creation of ntz txns is mostly complete, and is functional. Some refining still needed. To create a ntz tx, notary wallets will call the RPC method create_ntz_transfer

- The first two times that this method is called (performed automatically on notary wallet launch), the wallet paces the resulting pending_txinfo into a container. Since this RPC call takes between 5-15 seconds to complete, the cache will be used to speed up response time to the NOTIFY_REQUEST_NTZ_SIG protocol command, which is relayed automatically each time signatures are added, or upon creation of a new pending_tx

- Creation of  a notarization request is authenticated, and checked against the hardcoded pubkeys located in src/komodo/komodo_notaries.h.

3.)  Each notary node is given a signers_indexvalue, corresponding to their specific node. This value is appended to the index (which is an array, holding 13 values). Before signatures are appended, this field holds a default value of “-1” as a placeholder.  A partially signed transaction with a single signature will look like:
4.) An RPC method append_ntz_sig has been added to perform the act of appending further signatures/outputs to a pending_tx, relayed by NOTIFY_REQUEST_NTZ_SIG

Currently, relay messages via protocol are fully working for requests.

You can find more details on these methods, etc.  As well as how the mempool treats pending ntz txns differently from regular txs, in the README.md located here: https://github.com/blur-network/dpow-blur/blob/dpow/README.md

If you wish to help test these additions, and the new difficulty algorithm (Monero's DAA with 1 minute block times) which will both be added at the next hardfork (v11)...  a version 11 testnet is currently live and running with these changes.  You will need to compile the dpow-blur source to run a node on the testnet.

Use the flag --restore-deterministic

Good afternoon.
I have an old daemon and wallet version blur-v0.1.7-win-x86_64.
I used to update your binary file without any problems and transfer my wallet to it - there weren’t any problems.


I downloaded your new version - blur-v0.1.9.8.1-win-x86_64.
But my password from my old wallet does not work now.
What is the problem? What should I do and how to get my coins?
Thank you in advance.


I went into the old wallet and got my seed.
Then he tried to restore the wallet through his seed, but received an Error: Multisig seed failed verification error.
What am I doing wrong? How do I get my coins?

Sorry, I have not been checking bitcointalk often, as the development work on DPoW has been keeping me busy.  Things are at a very discernible point of functioning, from a wallet, daemon, and protocol-level standpoint.  I'll post an update here in a bit, on the development progress.  It's been a while since I updated everyone.  But have exciting things to share from code

Still a bit more work to go, but things are quickly getting closer to being done.

I look forward to the bounty program. I think this will statr as logical as I have very little information about the project.

Recent jump in hashrate / difficulty... roughly 3x from a few weeks ago. Any news on this?

Strato

Have you ever had similar project here at BCT? Seems like I've alreday seen such projetc here. Maybe i am mistaken though...

Would be nice to see the exchange coin. Will this be pump-and-dump coin, or a serious project, guys?

Please be advised: Terms & Conditions, and the Privacy Policy on the website have been updated. Please take the time to refamiliarize yourself with the existing terms & policies, as well as getting acquainted with the new ones

You can access the "Terms and Conditions" agreement here: https://blur.cash/terms-and-conditions

And the website's "Privacy Policy" here: https://blur.cash/privacy-policy

And as always, our "Mission Statement" is available here, for completeness: https://blur.cash/mission-statement

Note that these are also all accessible from the footer of the website's main page.

UPDATE: For those interested in progress on the DPoW integrations, the README in the DPoW-Blur repository has been updated!

You can access the repository here: https://github.com/blur-network/dpow-blur

Please note that the RPC methods included there are unfinished currently, but have partial functionality.

The ntz_transfer command issued to blur-notary-server-rpc will currently generate a single Tx with 64 destinations.  Subsequently, this transaction (signed by a single notary node) is relayed to the network as a request for more signatures.

Once the count for signatures reaches 13, the transaction will be relayed. You can simulate this behavior by changing sig_count to 13 in either RPC call:

1.)  request_ntz_sig sent to the daemon with a signed tx_blob

or

2.) ntz_transfer with sig_count = 13

Further functionality of authenticated tx creation, and automatic signing will be implemented in the next few days.

Hey, guys, good idea! Do you have a crypto-development background? Checked repository. It's straight-forward. How are people in your team?

Hope you will be doing good and this is going to be a success story I've heard something about this project from outside of this forum.

Libbtc has been added to the DPoW-Blur repository for Bitcoin transaction parsing.

Timeline has shifted back slightly on the DPoW integrations, as some may have noticed. Patching the vulnerability from the XMR wallet bug necessitated the immediate attention. DPoW code should be done in roughly two weeks, as a result.