ANNOUNCMENT: Binaries for Blur v0.1.9.9.6 ‘Radiance’ have been released!Executables have been uploaded to GitHub, for all platforms. Notable changes include:- Began adding supporting files for dpow-blur- Fixes a long-standing issue with sync, that was causing nodes to stall - Cross-compilation now working for all platforms (compiled from Ubuntu 20.04 host) - Updated workflows to compile on Ubuntu 20.04, as 18.04 has hit EOL - Changes to depends build system - Removal of expat package as optional dependency - Database modifications for storing of BTC transactions, parsed from BLUR tx extras - Compilation fixes for newer versions of GCC - Compilation fixes for newer versions of Boost (ASIO) - Resolves numerous compiler warnings Grab them here: https://github.com/blur-network/blur/releases/tag/v0.1.9.9.6 or by following the links at https://blur.cashChangelog may be expanded on Releases page at a later date. Snap package for CLI tools, and GUI wallet have also been updated. CLI Tools Install: snap install blurCLI Tools Update: snap refresh blurGUI Wallet Install: snap install blur-walletGUI Wallet Update: snap refresh blur-wallet
|
|
|
Progress Report for Week of March 15th - March 21st, 2021
Development Work Completed During Week:Repositories Updated:• blur-network/dpow-blur - Testnet repository for v11 network hardfork • blur-network/blur-explorer - Testnet explorer with v11 changes • blur-network/blur-api-cpp - Compatibility layer for cross-chain comms with KMD • who-biz/nntools - Notary node monitoring tools Development Milestones Reached:• Base58 encoding/decoding functions added to `dpow-blur` from bitcoin core • `blur-explorer` display style changes, code style updates to `dpow-blur` with recent btc-base58 additions • Efficiency improvements under-the-hood in notarization-related functions/operations in blur daemon ‣ Sync speed improved, by minimizing calls to expensive functions (notarization data is only polled when we add a new notarizing block to blockchain/DB successfully) • LMDB map resizing mechanics updated in `dpow-blur` to now match those present in `blur` core repo since v0.1.9.9.5 • Version for `dpow-blur` updated to `v0.2.0.0-testnet` • Fixed a bug which ignored incoming `ntz_sig` requests from peers if `target_height = 0` in `cryptonote_core` class ‣ This can happen, and is normal at `init`, and at points during protocol sync (particularly when we remove a peer connection) • Resolved a consensus bug in testnet which resulted from `komodo_update()` not being called at proper points in blockchain sync • Added support for `sig_count/signers_index` display for tracking of NN signer identities in Pending Notarization Pool of `blur-explorer` • Added support for graceful display of lengthy `tx_extra` field to Blur Explorer for notarization transactions • Successfully decoded `OP_RETURN` data from KMD notarization txs with embedded BLUR data Community Work Completed During Week:• Began participation in Komodo's 2021 Notary Node testnet • Began lightning Network research in conjunction with CHIPS project (KMD ecosystem) Goals for Week of March 22nd - March 28th:
Development Goals:• Add proper `decoderawtransaction`/`signrawtransaction` methods to `blur-api-cpp` compat layer • Ensure that `OP_RETURN` data being posted to KMD (for BLUR ntz txs) is correct ‣ Need to embed more data than `(genesis_block | height | BLUR | 0x00)` (currently what is being displayed in each) ‣ Above correction of `blur-api-cpp` methods should accomplish this • Make communication through blur-api-cpp bi-directional so that blurd can fetch information from `komodod` to embed in blur transactions • Continued testing wtih Komodo Community Community/Housekeeping Goals:• Further participation in 2021 NN Testnet, LN research with Chips • Shore up deployment procedures for Blur Notary Node setup • Improve procedure instructions, consolidate full setup into single deployment script • Update Roadmap for 2021, input milestones from 2020 not currently reflected on Roadmap • Set up section for Progress Reports on https://blur.cash/, automate publishing of these releases to Medium/Twitter
|
|
|
Progress Report for Week of March 8th - March 14th, 2021
Development Work Completed During Week:Repositories Updated:- https://github.com/blur-network/dpow-blur - Testnet repository for v11 network hardfork - https://github.com/blur-network/blur-explorer - Testnet explorer with v11 changes - https://github.com/blur-network/blur-api-cpp - Compatibility layer for cross-chain comms with KMD - https://github.com/who-biz/dPoW - Fork of Komodo's DPoW repository - https://github.com/who-biz/nntools - Notary node monitoring tools Development Milestones Reached:- Testnet explorer with real-time display of pending notarization in ntzpool/txpool is now live at https://testnetexplorer.blur.cash- Completed approximately 100 successful notarizations to KMD mainnet blockchain (partially valid) - Improvement of `dpow-blur` testnet synchronization speed by minimizing expensive calls to database - Added support for importing bitcoin-like public keys to blur daemon via `--btc-pubkey` commandline option - Addition of `scriptPubKey` generation for for valid mocking of BTC `P2PK` scripts(necessary for iguana transaction-handling) - Surpassed 1100+ notarizations on Blur Network testnet - Added support for pending notarizations to Blur Network Explorer - Forked https://github.com/who-biz/nntools from https://github.com/webworker01/nntools, for notary node data monitoring on Komodo - Successful testing with Komodo of blur<->kmd cross-chain comms - Resolved crashes in `blur-api-cpp` due to concurrent RPC calls for Blur chain data coming from iguana Community Work Completed During Week:- Discord bridge between Komodo Discord and Blur Network Discord has been created in channel #kmd-bridge, for live feeding of messages from their chat to ours - Began planning for participation in Komodo 2021 NN tesnet - Researched with help of Telegram community Member "Ultimate": ways to automate press releases for weekly/monthly progress reports (plan to use Zapier to post WordPress blog posts to Medium/Twitter) Goals for Week of March 15th - March 21st:- Continued testing wtih Komodo - Shore up deployment procedures for Blur Notary Node setup - Improve procedure instructions, consolidate full setup into single deployment script - Add `sig_count`/`signers_index` fields to explorer's Pending Notarization Pool - Make communication through `blur-api-cpp` bi-directional so that `blurd` can fetch information from iguana to embed in blur transactions - Update Roadmap for 2021, input milestones from 2020 not currently reflected on Roadmap - Set up section for *Progress Reports* on https://blur.cash, automate publishing of these releases to Medium/Twitter - Decoding of `OP_RETURN` data posted to Komodo's blockchain for BLUR notarizations, fetch data for publishing data to BLUR blockchain in back-notarization portion of feedback loop - Add `decoderawtransaction` to `blur-api-cpp` compat layer, make `signrawtransaction` functional rather than just a dummy method
|
|
|
Progress Report for Week of March 1st - March 7th 2021
Development Work Completed During WeekRepositories Updated:- https://github.com/blur-network/dpow-blur- https://github.com/blur-network/blur-api-cpp- https://github.com/who-biz/dPoWDevelopment Milestones Reached- Successful completion of Blur-side checkpointing scheme for eventual completion of DPoW - Thorough regression testing of blur notaries and consensus rules (~950 notarization cycles completed to date) - Fine-tuning of `blur-api-cpp` compatibility layer for interfacing with Komodo network - Mock bitcoin-like RPC calls between `blurd` and KMD's `iguana` for notary network testing functionally - Testing in conjunction with QA team at Komodo for future deployment and proper functionality Community Work Completed- Added a #github-activity channel in Discord for piping of github commits in major repositories to Discord - Established #weekly-updates-and-milestones channel in Discord for weekly progress reports and future goal setting - Began investigating bridge between Komodo discord's #blur channel, and our own - Looking into ways to automate these weekly progress reports and publish as press releases on both https://blur.cash and https://medium.com/blur-network- Opened dialogue with STEX exchange regarding possible listing, sent applications to a handful of other exchanges Goals for Week of March 8th - March 14th- Continued testing with Komodo and amongst BLUR notary network - Automation of press release publishing - Update roadmap on website for 2021 - Further exchange outreach - Get full notarization cycles working with `iguana` and a completed notarization to `KMD` chain - Make communicatin through `blur-api-cpp` bi-directional so that `blurd can fetch information from iguana to embed in blur transactions
|
|
|
Price jumping around, up 120% or so on Citex.me Exchange. What's up with txbit.io?
Cheers,
Strato
Hey strato. We are no longer listed on Txbit. We were included in a round of delistings they did due to low volume (KMD and a handful of other larger networks were also included in that delisting round). It appeared that our users were no longer satisfied with trading on their exchange after they implemented KYC. We were delisted sometime in the beginning of January. Citex, not sure. But we are still listed there. My guess would just be low liquidity. Cheers.
|
|
|
For those who are specifically interested in our work toward interoperability with BTC-like chains and Komodo's iguana... There is a compatibility layer currently under development here: https://github.com/who-biz/blur-api-cpp. Alternatively, it's also forked on the Blur Network org github: https://github.com/blur-network/blur-api-cpp. A big part of the delay and time estimation errors were reconciling not only different elliptic curves (in XMR-based code, vs BTC-based code), but also different JSON-RPC specifications. The blurapiserver (which can be built by compiling one of the repositories above) does the work of translating between JSON-RPC specs, as well as imitating bitcoind rpc responses. When "mocking" the responses over RPC, we simply plug in the data from our blockchain required for notarization ... and use mock values to pass iguana's validation, elsewhere.
|
|
|
DPoW?
There is a post here from march that says it is near completion. So 6 months from "near completion" and still no announcement? And that announcement was a year past the self imposed deadline.
Time to call time of death on this one
Please check our channel in the Komodo discord. You'll find that development is still quite active, and we are working with multiple devs/notary node operators from KMD. Timelines are difficult when designing interoperable solutions. Real tech takes some time to build. Sit tight 
|
|
|
ANNOUNCEMENT: Snap packages for v0.1.9.9.5 have been released!These upgrades incorporate the changes from latest point release to each package. Links to Snapcraft pages:Command-Line Tools: https://snapcraft.io/blurGraphical Wallet: https://snapcraft.io/blur-walletHow to upgrade your current installation:Command-Line Tools: snap refresh blur Graphical Wallet: snap refresh blur-wallet How to install:Command-Line Tools: snap install blur Graphical Wallet: snap install blur-wallet Additionally, the icon for the GUI's desktop integrations has been changed from a PNG to an SVG, since the former was not scaling properly. This led to a pixelated icon in desktop menus/launchers. You'll find things much crisper looking upon updating.
|
|
|
A graphical wallet for BLUR is now available in a snap package!Complete with desktop integrations, and one-click mining! Grab it here: https://snapcraft.io/blur-walletOr with snap install blur-wallet
|
|
|
Binaries for Blur v0.1.9.9.5 'Radiance' have been uploaded to GitHub!Grab them here: https://github.com/blur-network/blur/releases/tag/v0.1.9.9.5Notable changes include:- Simplification and speedup of dynamic portion of proof-of-work algorithm - Quicker connection with the network due to seed node addition on daemon initialization - Auto-resizing of database while running (no restart required) - More efficient use of space on disk by DB, and more efficient resizing mechanics Changelog has more details on the above.
|
|
|
Blur was recently featured on the first ever episode of Gigacast, on The Daily Chain!Check it out here: https://thedailychain.com/gigacast-episode-1-meet-biz-lead-dev-of-blur-network/This podcast is only about 30 minutes in length, but packed full of information about Blur, DPoW, current development progress, and our collaborations with other projects! The podcast with MineYourBiz was over an hour, so for those who might not want to listen to that long of an interview, this one might be more your speed.
|
|
|
BLUR was recently featured on a MineYourBiz video interview!Check it out at the following link to hear our lead developer Biz talk with Seth Estrada about DPoW, BLUR, privacy, crypto, and much more! https://mineyour.biz/blur-network/
|
|
|
guys stay away from this coin ,it doesn't smell like decentralization,the developer is not sure that he has the right to warn the exchange about the upcoming update and as a result ,people lose their assets, and when you tell them about it directly, you are simply banned.
I’m not sure what this is about. We will be contacting all exchanges to ensure that they update by the TBD fork date (we haven’t had a network-wide update in around a year). No one has lost assets on an currently listed exchange that I’m aware of. All of the exchanges we are currently on, are extremely active in terms of support. That said, if you feel you’ve been mistreated or have lost coins, provide some proof and we’ll help out in what ways we can do so.
|
|
|
So this coin can now be gpu and pool mined. The blur team did not believe me when i said their coin could easily be both gpu and pool mined. So i did it to prove to them how easy it was and to demonstrate how the recent nethash gains could be gpu miners. So here is a pool for y'all http://167.86.119.62:8080and you can get a miner (nvidia only, amd is wip) by building the source code at https://github.com/fart-master/blur-minerBTW, how is dpow going? I saw this Integrations are looking like they’ll be done around the end of June. Possibly a week or two into July. it is now the end of November Dear all, Can you please send us cpu miner for windows. Thank you, Djurica Miner is embedded in the daemon. There are instructions in the README here: https://github.com/Blur-network/blur
|
|
|
DPoW development is indeed coming along nicely Very close to completion, at present.
|
|
|
A snap package for the Blur Network GUI (Graphical Wallet) has been released, as well as an update to v0.1.9.9.2 for the CLI Tools snap package!This packaging makes the GUI available on most distributions of linux, and retains all functionality of the blur-network-gui repository's releases. Snap packaging seems to make networking/connectivity markedly smoother, as well as potentially making the GUI more private and secure. This is due to the unique confinement feature of snaps. Grab the package here: https://snapcraft.io/blur-walletOr simply install it with a sudo snap install blur-wallet Once you've downloaded it, you can run the package with the command blur-wallet from a terminal. That command will launch the GUI interface. Support for standard desktop launchers may not yet work. Please let us know if they (i.e. Start Menu) work for you! Command-Line Interface:https://github.com/blur-network/blur/releasesBlur Network CLI Tools Snap Package: Or install with: sudo snap install blurWhen launching the snap, include the startup flag blur.blurd --p2p-bind-port=52541 for the best network connectivity.Graphical Wallet:https://github.com/blur-network/blur-network-gui/releasesBlur Network Graphical Wallet Snap Package: Or install with: sudo snap install blur-walletRun with 'blur-wallet' from a terminal, once installed
|
|
|
dev f*cked the community by abandoning the project. no revival attempt will succeed. stay away from this scam.
Indeed. Their discord is quite interesting... dev leaves, comes back not even a day later, says the project isn't supposed to be a currency nor have monetary value, won't prove he didn't dump his premine funds, largely writes off the KMD dpow implementation he was working on in an effort to secure directly with BTC, and then leaves again. The project is in complete disarray... when you have an unstable dev like this, especially the sole dev, it's hard to have faith in the project. Glad I'm observing as an outsider. Good luck to all those still stuck in this dumpster fire. Wait for the dust to settle, the original dev leaving might be the best thing that ever happens to Blur, seriously, if the community steps up like what happened with Monero after their original dev left, Blur could attract a lot of new talent, like XMR did. Fluffypony, smooth moneromooo tacotime etc, none of those guys started Monero, they came after the genesis dev left Edit, none of these guys are the dude who started monero https://web.getmonero.org/community/team/Blur community is open for new talent looking for opportunities, so many other cryptos have gate keepers blocking who can do things, Blur doesn't have that problem, and either did monero after the genesis dev left. Funny, a top 20 crypto that I use for years and I can't even remember the Monero genesis devs name ... That's a selling point  We are very much open to new contributors and any assistance that the community can volunteer. Contributions are evaluated based on their merit, and we don't ever say "no" to ideas. Thanks for the support and for believing in Blur! We have only been able to keep going, thanks to the massive response we got from community members willing to help out. While we do now have enough hands on deck to keep things properly decentralized on the administrative-side of things... We can always use more. Drop by our discord chat, post a message, and we'll see how your skills might fit into our current committee. Please note: We are driven entirely by volunteer efforts. Unfortunately, we can't provide bounties for work, etc. Community funding can be inquired about, directly to the community members in-chat, though.
|
|
|
dev f*cked the community by abandoning the project. no revival attempt will succeed. stay away from this scam.
Indeed. Their discord is quite interesting... dev leaves, comes back not even a day later, says the project isn't supposed to be a currency nor have monetary value, won't prove he didn't dump his premine funds, largely writes off the KMD dpow implementation he was working on in an effort to secure directly with BTC, and then leaves again. The project is in complete disarray... when you have an unstable dev like this, especially the sole dev, it's hard to have faith in the project. Glad I'm observing as an outsider. Good luck to all those still stuck in this dumpster fire. Wait for the dust to settle, the original dev leaving might be the best thing that ever happens to Blur, seriously, if the community steps up like what happened with Monero after their original dev left, Blur could attract a lot of new talent, like XMR did. Fluffypony, smooth moneromooo tacotime etc, none of those guys started Monero, they came after the genesis dev left Edit, none of these guys are the dude who started monero https://web.getmonero.org/community/team/Blur community is open for new talent looking for opportunities, so many other cryptos have gate keepers blocking who can do things, Blur doesn't have that problem, and either did monero after the genesis dev left. Funny, a top 20 crypto that I use for years and I can't even remember the Monero genesis devs name ... That's a selling point  I don't think it will recover and i don't think any other dev will join. Everyone who opens his mouth in there gets banned. It will get worse now because the current mods are complete idiots, even more so than biz was. This is a Haven like exit scam and it is going into round 2 now. I pitty those who have not sold yet. This is kind of funny, because I wrote the first article predicting the Haven fallout that would come around a year afterward. Link: https://whalereports.com/the-munnypot-2-haven-protocol-xhv-a-critical-review/
|
|
|
|