Pages:
Author

Topic: [ANN][ZANO] New Sources|1st ProgPowZ|PoW/PoS Hybrid|Scalable|Private|Contracting (Read 36422 times)

sr. member
Activity: 519
Merit: 252
555
Anyone here? The Zarcanum update seems to have broken PoS mining for me, and I've filed a bug report. However, I wonder if it's a simple issue on my end, so I'd appreciate any ideas:

https://github.com/hyle-team/zano/issues/437

Edit: I think I fixed it, using a new wallet as it was suggested somewhere for the Zarcanum update.
sr. member
Activity: 1008
Merit: 391
legendary
Activity: 3122
Merit: 1003
This project still alive?

Of course it is... very much alive.
member
Activity: 229
Merit: 45
newbie
Activity: 21
Merit: 0
We are excited to list Zano on Seven Seas. They are doing big things in the privacy space. We love it!

ZANO-BTC trading is live here: https://sevenseas.exchange/market/ZANO-BTC
legendary
Activity: 3122
Merit: 1003
    

   Is there a bootstrap?  Smiley
jr. member
Activity: 125
Merit: 1
newbie
Activity: 2
Merit: 0
Vote for Zano daily at CoinMarketLeague! Zano is soon to be in the top 25. Let's make it top 5!  https://coinmarketleague.com/
newbie
Activity: 2
Merit: 0
At Decapool (https://decapool.net/) Zano mining pool, 500 extra Zano have been donated by Gigabyted to pay miners a promotional extra 10% per block found! In addition to the usual proportional rewards that are split up to all miners.  The usual 1% finder / 1% pool fee apply to the base block reward, and an additional 10% reward is given to the block finder aka "Promo Reward."  This is an incentive for miners to switch away from luckypool (over 90% of PoW blocks on the network are found by this pool) as the total Zano reward per block is 10% higher than any other pool and the block finder gets the additional 10% (0.1 Zano) for every block found!  This has been made possible by Gigabyted 's 500 Zano donation to the Decapool.net wallet.  This promo will only last as long as the 500 funded Zano last (5000 blocks found on the proportional side of the pool).  This promo does not apply to the Solo pool.
legendary
Activity: 3122
Merit: 1003
is it still possible to swap Boolberry BBR for ZANO? If so, how? Thx

Sorry, but the swap ended long ago. You can exchange BBR to BTC and then to ZANO if you like.  Smiley
newbie
Activity: 6
Merit: 0
is it still possible to swap Boolberry BBR for ZANO? If so, how? Thx
hero member
Activity: 976
Merit: 646
Hello everyone!
Congratulations on the project's birthday (the third one!), and we are happy to announce that we are rolling out a new release with Tor support out of the box! This build does not install any additional components to support Tor. Instead, we natively implemented protocol support, avoiding the need to keep the loaded Tor network service in memory all the time. It was a big and challenging job since such libraries did not exist before, and we put a lot of effort into achieving this result. In addition, we have closed all the "issues" in GitHub (but @musclesonvacation recently managed to write new ones), and a lot of fixes and improvements have been made based on those reports.
Thanks to everyone for your support and collaboration!

Release short rummary:
  • !!!Added TOR support for transactions relaying(both simplewallet and UI)!!!
  • predownload bumped up to 1569k
  • wallet: minor htlc error-handling improvement
  • Fixed multiple minor issues #262, #319, #318, #284, #277, #262
  • Implement smart blacklisting of wrong nodes (#293)
  • Fixed multiple UI artefacts
  • Added command line option to disable price fetching from GUI wallet (#315)

FYI: With this new release, we added lib OpenSSL to dependencies (and added instructions for it's setup in readme), also, we have changed the minimal Boost version to 1.70 due to the latest changes in the codebase.

https://github.com/hyle-team/zano/releases/tag/1.5.0.143

newbie
Activity: 28
Merit: 0
Some free project feedback:

Zano lacks a clear communicable vision, unique value proposition along with a general ecosystem. This is reflected by its general lack of market interest, adoption and capitalization growth.

The website has multiple milestones marked as planned, under development or completed; but someone from the outside looking in at these milestones has no clue how they all mesh together to form a unique value proposition that will positively impact the world. As a result, they are left to speculate their own conclusions on what problem Zano is solving or which market is being addressed and these might not be based in reality.

A successful project needs to have a unique value proposition that resonates within a community that forms around an ecosystem; otherwise they are building a solution for a problem that doesn’t exist. This is an obvious conclusion if one looks at Zano’s long term performance in market capitalization, which, unfortunately seems to be following the same footsteps as Boolberry unless there is a positive change moving forward to reverse that trend.

After reviewing the roadmap milestones on the Zano website I have come to the conclusion that the most viable option available for Zano is pivoting away from whatever its current unknown direction and into one that caters to patrons of the NFT market. A privacy preserving digital art gallery where buyers and sellers along with their transactions are anonymous. This is something that just isn’t possible on Ethereum or Solana and is preventing the sector from reaching its true potential.

Some real world examples pertaining to the current sales of NFT artwork on said networks:

1 - Sealed art bidding protects bidders from having their wallet balances used against them
2 - Financial and personal privacy for artists i.e. Banksy (https://en.wikipedia.org/wiki/Banksy)
3 - Private art ownership

In many aspects the current NFT art market is a digital reflection of the physical art market. The latter being one of the oldest markets that has maintained a firm foundation in the preservation of privacy: from the confidentiality of buyers and sellers to the value of the item sold. All these aspects present the perfect product market fit for Zano which at the moment is still unknown. While art is just one vertical in the NFT market it provides a solid basis for Zano to expand into the verticals.

Zano already has the majority of the building blocks available in the roadmap to make this a clean and nondestructive pivot in terms of a functioning NFT on Zanochain through the existing on-chain address aliasing, marketplace, privacy enhancements and efforts towards an efficiently scalable blockchain. It can provide the unique value proposition that the project is missing and help create an ecosystem that can drive adoption and growth.

For example, the marketplace can be called “zGallery” with "zNFTs" or whatever else works to distinguish it from the underlying currency and traditional NFTs.

Gallery: “a room, series of rooms, or building devoted to the exhibition and often the sale of works of art.”

Below is a clear and concise mission statement that provides zero confusion for potential onlookers on what is being developed or its designated target market:

“Zano — an efficient NFT ecosystem built for confidential transactions between private parties.”
hero member
Activity: 976
Merit: 646
New ZANO pool, unique code

https://zano.supportcryptonight.com/

Mining Pool Address: zano.supportcryptonight.com
Ports:
6646 - Low end hardware
6647 - High end hardware
6648 - Nicehash/ MRR

1% pool fee
EU fast server
Spread some hash and try it.


Great news! Thanks!
legendary
Activity: 3122
Merit: 1003
New ZANO pool, unique code

https://zano.supportcryptonight.com/

Mining Pool Address: zano.supportcryptonight.com
Ports:
6646 - Low end hardware
6647 - High end hardware
6648 - Nicehash/ MRR

1% pool fee
EU fast server
Spread some hash and try it.


Why don't you list it here? >>       https://miningpoolstats.stream/zano
jr. member
Activity: 125
Merit: 1
New ZANO pool, unique code

https://zano.supportcryptonight.com/

Mining Pool Address: zano.supportcryptonight.com
Ports:
6646 - Low end hardware
6647 - High end hardware
6648 - Nicehash/ MRR

1% pool fee
EU fast server
Spread some hash and try it.
hero member
Activity: 976
Merit: 646

Hey everyone!
Great news!

Zarcanum — A Private Proof of Stake Scheme with Confidential Transactions and Hidden Amounts 

https://blog.zano.org/zarcanum-a-private-proof-of-stake-scheme-with-confidential-transactions-and-hidden-amounts/

Help spread the word: https://twitter.com/zano_project/status/1474003786607829005?s=20



newbie
Activity: 21
Merit: 1
Other ToR implementations works as a resident process/daemon, which is not suitable for mobile application, we wanted to have light implementation which create "circle" and deliver tx to outer world. Also, tx itself is not something private - this info is absolutely public, so exit nodes won't hurt any privacy aspects of transaction, only if someone can re-construct full circle of onion route and figure out ip address, which i guess quite hard with ToR.


Yes, figuring out IP addresses with Tor is quite hard precisely because of the mitigations stated above, which don't exist in tor-connect. Hence my reluctance of the use of this new and quite experimental library.

There is also a misunderstanding of what is currently a threat with using exit nodes : it's not per-se the information exchanged, which as you stated is public, the real risk here is a DoS and a fragmentation of the network. There is more details of these attacks on the research I linked in a previous comment.

This is also why I asked if onion services will be enforced by default, because it mitigate all of these risks. Basically, using Tor without enforcing the use of onion services (for full nodes, light wallets are not concerned) will do more harm than good privacy and security wise. And even if enforced, the effectiveness of it will largerly depend on its 'good' implementation by the developers, Tor is all but a silver bullet and require a deep understanding of its functioning in order to be effective.

Using the official Tor code/library would be a huge gain of time, while simultaneously more private and secure. I do understand that it took (maybe a lot of) time to develop tor-connect, and that it feels annoying not to use it, but still going for it just for that reason would be a sunk cost fallacy as there isn't objectively any good reason to do so.
hero member
Activity: 976
Merit: 646
Yes, it will be enabled by default.

Awesome !

We already got thin TOR library, you can take a look into it if you wish: https://github.com/hyle-team/tor-connect

Oh, I wasn't expecting a full reimplementation of the Tor stack. Is there any particular technical reason to do so that I am missing ?
Because there's so many ways it could go wrong : no padding, no guard rotation, no stream isolation, no pluggable transport for censorship resilience, nor every other crucial security/privacy features that Tor have implemented over time.

If this is only a matter of porting the Tor build process to CMake, which I believe has already been done by other projects, maybe it would be more interesting to go that way than reinventing the wheel ?

Other ToR implementations works as a resident process/daemon, which is not suitable for mobile application, we wanted to have light implementation which create "circle" and deliver tx to outer world. Also, tx itself is not something private - this info is absolutely public, so exit nodes won't hurt any privacy aspects of transaction, only if someone can re-construct full circle of onion route and figure out ip address, which i guess quite hard with ToR.



newbie
Activity: 21
Merit: 1
Yes, it will be enabled by default.

Awesome !

We already got thin TOR library, you can take a look into it if you wish: https://github.com/hyle-team/tor-connect

Oh, I wasn't expecting a full reimplementation of the Tor stack. Is there any particular technical reason to do so that I am missing ?
Because there's so many ways it could go wrong : no padding, no guard rotation, no stream isolation, no pluggable transport for censorship resilience, nor every other crucial security/privacy features that Tor have implemented over time.

If this is only a matter of porting the Tor build process to CMake, which I believe has already been done by other projects, maybe it would be more interesting to go that way than reinventing the wheel ?
Pages:
Jump to: