I'm working on a Antminer T17 and this was a verified working board, but for whatever reason it stopped working. Using a STASIC hashboard tester, I isolated the issue to the first domain region. The LDO is measuring 3.2v, but should be 1.8. The other domains are measuring 1.8, but I'm unsure what's the cause of it because this is the FIRST domain and what comes before this? Pics below:



https://prnt.sc/rmzqDEcmiOUs

Monero has a fork called Loki for those that haven't heard about it. Any thoughts on it?

From my research its the only monero fork that isn't just a monero clone with some numbers changed. They've implemented an interesting incentive model using their nodes to replace the Tor network. Does anyone know other projects that are working on something similar?

What intrigued me was that each master node is like an exit tor node, and if traffic gets routed to it, the node operator gets a payout. Users of the Lokinet (mixnet) don't need to hold any loki, its free to use just like Tor.

[hide or shorten text]

I made a chrome extension that resolves the following new handlers. This gives the ability to hide or shorten text on any web page. All alias data is stored on the Decentralized Ardor Data Cloud (https://ardorplatform.org/ardor-child-chain-feature/data-cloud)

btc:// eth:// xmr:// ignis://

And also we support the OpenAlias protocol: https://openalias.org -- This does a DNS lookup and doesn't use the Ardor blockchain at all.

openalias:// and oa://

Examples - Install Extension and visit this page again:

btc://longtext

eth://shorttext

xmr://myaddress

openalias://getmonero.org

oa://openalias.org

You can also paste the handlers into google search and it will output aswell.




Chrome Extension:

https://chrome.google.com/webstore/detail/blockchain-gateway/mcppmdjlghmadabjofodajpppiloembp

Feedback would be great... Thanks!

[Abstract:]

I've been learning about how the bitcoin blockchain works and a few other chains related to data storage. I wrote up an idea I'd like to get some feedback on which relates to extending Bitcoin's protocol with another blockchain without the need to change anything in the Bitcoin system. It doesn't have to be specifically for btc, but it can be used on any blockchain technically. I know sidechains involve the issuance of btc into the sidechain system, but in this scenario there isn't the need for any of that. We're just using the 2nd layer chain just for data storage that links back to BTC addresses.

Let me know what you guys think!

I have a rough prototype working, but still need to fix up some stuff.

--------------------------------

Blockchain Agnostic Proposal for Text Data Storage on a Sidechain

Abstract: Attach text data to any type of blockchain transaction or address without bloating the main chain and off loading this data to a secondary blockchain protocol or sidechain without changing anything with the main protocol.

Introduction: All blockchain implementations involve transactions from a sending address to a receiving address. These transactions are tied to a unique transaction id. Knowing these 3 unique data strings, we can use this information in the secondary layer blockchain for storing this data. This gives the ability to add uncensorable public messages or arbitrary text data to any transaction id or address in any blockchain system.

All blockchains have the following characteristics:

1. Transaction Id Address (TA)
2. Sending Address (SA)
3. Receiving address (RA)

Not all blockchain systems were made to store text data, as this would cause blockchain bloat over time. A solution for this is to off load this external data onto a secondary blockchain layer made for for this purpose while keeping the unique identifier in tact and linking it to the data.

This 2nd layer blockchain (sidechain) must be able to store arbitrary text data and be able to query this data via the main chain's addresses (TA/SA/RA). By referencing one of the main chain's addresses (TA/SA/RA) in the sidechain, we are able to pull all related data for this address.

To prove one of the main chain's user has sent the message to another address. The solution to this would be signing a message of the owners sidechain address with the owners main chain private key. Then, make a transaction on the sidechain with the public address and signature to prove the main chain's address owns the sidechain address.

Example Goal: Alice owns the address 15tYFmUV6wG4e1Gbi1buxBM9zSQzcWSkiK and Bob wants to attach a message "hello world" to this address.

Solution: Bob would first generate an account on the sidechain, then create a signature using the main chain's private key and sign the message of his newly made sidechain address. He would then make a sidechain transaction attaching the data: <main chain public key> <signature>. This now proves his <main chain's address> owns his <sidechain address> and vice versa. Now Bob can make a sidechain transaction attaching the message: <Alice's main chain address> <message: hello world>

To create a link of these 2 blockchains, wallet and block explorer developers would need to parse both chains to make this link by querying the sidechain for the main chain's public address.

The format of this public data would be: <address identifier> <message>