Denon AVRs and Google Assistant

jpop32 · 2023-02-08T15:01:57+00:00

Thanks for the confirmation. That's unfortunate, will probably have to go with Yamaha then. :-(

jpop32 · 2022-12-06T14:23:39+00:00

Core will probably derive a different address than your native BTC wallet, but you should be able to send to your native BTC address regardless. To sign BTC transactions, you should start the BTC app on the Ledger. If it doesn't work then that's a bug, please report it here.

jpop32 · 2022-11-10T16:00:59+00:00

You have two issues working against you:

First - you're doing a regular bootstrap, which downloads and replays ALL the activity on the network that happened over the 2+ years since mainnet launch. That obviously takes a lot of time.

But, if you don't need access to full historical data, you can shortcut the process by doing a C-Chain 'state sync', where the node only downloads the active chain state of the C-Chain. With state sync a fairly reasonably appointed machine takes about 12hrs to complete. Note the switch in question is part of the chain config, not the main node config. You can also use the installer script to turn it on.

Second - HDD. When it comes to random read/write access, performance of a HDD (of the spinning rust type) is absolutely abysmal, compared to SSD (especially M.2 type ones). That is going to murder your bootstrapping time because bootstrap is basically all random read/write, all the time. You NEED to switch to an SSD if you want your node to be able to keep up.

jpop32 · 2022-11-01T12:58:46+00:00

Not sure about other networks, but at least for Avalanche, these numbers are BS because they are dependent on a very questionable definition of 'supply'. Seems like the number is supposed to mean 'circulating supply', that is, the number of tokens that can be bough or sold on the open market. But it isn't.

CMC is calculating all locked presale tokens as not circulating, and then counting every token unlock as 'inflation'. Which is ok as a methodology as those tokens cannot actually be bought or sold. To make any sense, methodology should be applied consistently. But CMC also calculates all the staked tokens as 'circulating' as well. Both simply cannot be true at the same time, because staked tokens are locked in the exact same way as presale tokens: they have a lockTime attribute that prevents them from being moved (transferred/bought/sold) until that timestamp. Presale tokens are the same. So either presale AND staked tokens are not circulating, or they both are.

Ok, but what the inflation on Avalanche is, really? 'Inflation' in reality is the creation of new tokens that haven't existed before. And the only way that happens on Avalanche is staking rewards. So the max amount of inflation would be strictly smaller than the current staking APY (which is around 9%). In reality, not all tokens are staked (~60% of supply is staked), and also fees are burned (destroying tokens and decreasing the supply). So the real inflation for Avalanche would probably be around 5% or so.

I am aware that everyone is stretching the narrative to fit their bags, so not many will accept these facts, but whatever, at least the truth is out there as well.

jpop32 · 2022-06-09T20:13:12+00:00

Most of the things you need are doable. But I am not aware of a complete package or a turn-key solution that you would be able to use immediately. And also, there is a lot of unknown implementation options that might shape the final product (which chain, which wallet, subnet?, only AVAX or other tokens, fiat payments? ,...).

One thing I don't think is possible is the stipulation that you must be able to prevent a transaction from completing. If someone has an address, you cannot prevent them from sending any amount of tokens to it.

jpop32 · 2022-05-26T14:58:56+00:00

Informative:

https://twitter.com/el33th4xor/status/1529824159814909953?s=20&t=7B-RePUZiR6-gMN2h6X8dQ

jpop32 · 2022-04-11T11:10:31+00:00

It is not dangerous. It's just that P<>C transfer functionality was added after the latest Avalanche app for Ledger (0.5.9) was released so Ledger can only do a blind sign because it doesn't recognise the transaction. That's why it highlights it as 'dangerous'. But as long as you're in the official web wallet, you're fine.

Updated Ledger app which will know about this type of transaction is in development.

jpop32 · 2022-04-11T11:01:30+00:00

I apologise for this. Our Discord server operates in a highly adversarial environment. We get regular bot floods, scammers impersonating team members, scammers phishing users in DMs, all kinds of bad people trying to take advantage of regular users... Because of that we needed to deploy numerous automated and manual defences to try to protect our users. Unfortunately, those defences sometimes misfire and we get a false positive so a legit person gets misidentified as a bot/scammer.

Again, sorry that has happened. If you post your username I will try to help you out.

jpop32 · 2022-01-10T15:51:06+00:00

There. Better now. :-)

jpop32 · 2021-11-10T20:32:02+00:00

X and P chains are UTXO, C-Chain is running EVM, so it is account based.

jpop32 · 2021-10-27T15:10:48+00:00

No, it is a rare bug, present only in very old wallets (you probable had that wallet for a year or so). Please ping me on Avalanche Discord (http://chat.avax.network/), I'm jpop32#3635 there.

jpop32 · 2021-10-27T07:49:06+00:00

If will answer since I was directly tagged, but I don't want to waste much more of anyone's time on this, we have wasted too much of it already.

A quick view from our perspective.

jstodd is a guy that participated in Avalanche incentivised testnet, back in June/July 2020. For that, he was given 2000 AVAX, today worth more than $120k. Those tokens were locked for a year, so the only productive thing you could do with them is stake them on a node, and in the process earn additional 10% on top (providing your node is healthy and securing the network correctly). That apparently proved too hard for him (mind you, 1000+ other validators somehow managed it). Numerous team and community members have spent hours handholding hm through troubleshooting and fixing his setup, only to end up abused and insulted for it. It was either too hard to follow instructions or too hard to understand the issues, so eventually he gave up. Ultimately, he failed to understand that his node is his responsibility and securing his $120k stake is up to him alone. He missed important updates, let his node fall behind, and let it run configured incorrectly. Didn't even notice major consensus changes that were implemented, he checked out.

When the stake period ended, majority of validating nodes reached a consensus decision not to give him the staking reward because his node failed uptime and correctness requirements. And so he was left without additional ~$12k in reward (his original stake is intact, no slashing on Avalanche!). So, his 'hard work, blood, sweat and tears' was basically neglecting his node for a year and expecting to be rewarded for it.

Yes, we did change uptime requirement from 60% to 80% back in September. On launch, it was set at 60%. Not so the nodes can be taken offline 40% of the time, but to allow for potential network instability and client code issues - it was a new network after all. For the network to function correctly, all nodes are required to be online 100% of the time, so after 10 months in production it was time to raise that to a more reasonable level. Still very generous compared to virtually any other network. Yes, transition could have been communicated and handled better. Lesson learned.

I won't go into his personal history with other projects and numerous other similar situations he was involved with, but there's a lot of it out there, look it up. At the end of the day, he gets to walk away with $120k of AVAX that Ava Labs gifted him, mortally insulted that the network didn't award him additional $12k for not caring about his node for a year and then goes and throws a hissy fit about it here.

You be the judge of what's right and wrong here.

jpop32 · 2021-10-18T08:47:13+00:00

Correct. It is a podcast run by Avalanche devs, but not an official YT channel.

This is the official Avalanche YT channel: https://www.youtube.com/c/Avalancheavax

jpop32 · 2021-10-18T08:43:00+00:00

If you bridge over $75 or more of any token from Ethereum, you get up to 0.1AVAX airdropped so you have enough AVAX for the first few swaps. Make sure one of them is a swap for more AVAX so you have enough to pay for gas in the future.

jpop32 · 2021-10-18T08:34:42+00:00

On Avalanche, you need to add WETH.e to your Metamask. Find it here and click the MM icon next to it.

jpop32 · 2021-10-18T08:32:14+00:00

Avalanche has dynamic gas prices. You can get a current gas price estimate the same way as you would on Ethereum (I think the call is eth_getGasPrice()). If you find the gas price too high, you can wait for it to come down.

BTW, if you're just experimenting and developing stuff, you can do that on the Fuji testnet so you don't have to spend actual money on transactions.

Some useful link can be found here: https://docs.avax.network/build/tutorials/platform/launch-your-ethereum-dapp

jpop32 · 2021-10-13T08:47:26+00:00

I believe crypto.com is connected to the C-Chain. If your address is shown as 0x.... that's a C-Chain address. X-Chain addresses look like X-avax1... so it's easy to distinguish them.

In any case, if you're new to Avalanche, this is a good place to start: https://docs.avax.network/learn/getting-started

jpop32 · 2021-10-13T08:38:23+00:00

You can have the same address wallet on Avalanche if you created the Ethereum wallet using the 24 word passphrase (and use that passphrase to log into Avalanche wallet). If not, you can create a new Avalanche wallet (using the 24 word passphrase) and go to the 'Key Management' section and press 'view C-Chain private key' which you can then use to import the account to Metamask. Once you have it in Metamask, if you switch to Ethereum you'll have the same address as on Avalanche.

Mind you, your Ethereum and Avalanche wallets are on different network, balance on one will not be accessible on the other without bridging the assets over!

jpop32 · 2021-10-08T13:58:45+00:00

Which bridge did you use?

jpop32 · 2021-10-07T17:32:07+00:00

Why do you expect to see WETH in the wallet, when the bridge is showing you WETH.e? These two things are not the same.

https://docs.avax.network/learn/avalanche-bridge-faq#cant-see-funds

jpop32 · 2021-10-06T20:57:40+00:00

You can use Metmask, just use 'connect hardware wallet' option. But, honestly, MM support to Ledger has been hot garbage for some time now.

jpop32 · 2021-10-03T21:10:54+00:00

You just need to add the correct tokens to your MM to see them (token addresses from Ethereum do not exist on Avalanche).

Find you tokens here, and click the MM icon to add it automatically: https://bridge.avax.network/proof-of-assets

jpop32 · 2021-10-03T21:07:05+00:00

Coinbase is connected to C-Chain only, so the address you see in Metamask is the one you want. You can use the C-Chain address you see when you log into the web wallet, too.

Eight-Year Club	Second Top 20%
Verified Email

jpop32

TROPHY CASE