Мне уже неоднократно удавалось вернуть токены знакомых, которые по ошибке переводили их не на ту сеть на биржах например в место эфирной сети отправляли в сеть Matic. Когда тех поддержка видит, что ты технически и юридически грамотный и не собираешся с них слазить, то как правило идут на уступки. Кстати им ничего не стоит отправить вам приватник и затем сгенерировать новый, но вместо этого они предпочитают внушать тебе что ты сам дурак и лох, а токены со временем присвоить себе.
Сейчас бинанс всем внушает, что все должны быть верифицированы и жить по закону, так пусть сами показывают пример и не присваивают чужое.

Водить за нос и наживаться на не внимательных пользователях - обычная практика любой криптобиржи. Пока вам поддержка включает дурака вполне корректно говорит, что функционал ихнего кошелька не позволяет переводить NFT и проверить, правда это или нет непредставляется возможным.
Вам нужно написать им, чтобы они импортировали приватник от вашего адреса в кошелек, который поддерживает работу с токенами формата ERC 721 и вывели вам NFT за вознаграждение, или если у них не достаточно квалификации проделать данную работу, то вы готовы самостоятельно все сделаьть. От вас только требуется выслать приватный ключ.
Далее импортируете приватник например в MyEtherWallet, пополняете адрес эфиром для оплаты комиссии, выводите NFT.

В случае отказа обьявите им, что считаю вас изменниками и разбойниками, намереваюсь драться с вами, донимать осадой, приступом или иначе и чинить вам всякую досаду и разорение. закидаете их негативными отзывами на форумах 

Для того, чтобы отослать назад вам NFT, бинансу прийдется заплатить самим комиссию в эфире (а зачем им такое счастье надо?)
Тут два варианта: или просить чтобы отсылали назад NFT за вознаграждение, или чтобы выслали вам приватный ключ от этого адреса и вытягивать от туда NFT самому.

The more bits you disable, the easier it will be to detect the "unnatural" operation of the fake generator. There must be a compromise, you must turn off so many bits that you yourself cannot go over everything quickly knowing the mask. You must have a computer with several powerful video cards on which the search time can be, for example, 1 month. In addition to the example I described above, you can run the result of the fake generator through the SHA-256 function to mask a large number of disabled bits.

To create a fake random number generator, there is no need to create any databases, especially since there is nowhere to store them in the hardware wallet. To generate non-random 24 words, you need to create a 256-bit mask that will disable certain bits (set to 0) from the number generated by a real random number generator. Each disabled bit will reduce the search time of the seed phrase by 2 times.
An example for an 8 bit number:
10010101 - random number
    “AND”   - logical multiplication
00011001 - mask
      =
00010001 - fake random number
When iterating over a number, we only need to iterate over 1, 4 and 5 bits, since the rest of the bits will be guaranteed to be 0.
In this example, the search time will be reduced by 32 times.
The attacker will have to periodically perform a complete search of the seed phrase using the mask he has created and check the positive balances.

Alternatively, if you want to store large amounts and do not trust the built-in random number generators, you can buy, for example, a Keystone wallet and use it only to generate seed phrases using dice, and then use this seed in other hardware wallets.
It would not be bad if someone from the manufacturer created a separate inexpensive device for generating seed phrases using dice or coins, and also had a built-in mnemonic converter Ian Coleman.

Not quite clear what you mean?
The wallet, having generated a random number (for example, 256 bits), adds 8 bits of the checksum and sends it to a function that converts it to base 2048 and outputs 24 numbers of 11 bits each, which is then replaced with the corresponding word from bip39 dictionary. All this is easily verified.
Or do you think there may be a second fake random number generator in the wallet?

dkbit98 это известный хэйтер Ledgera и других кошельков с закрытым исходным кодом. Я бы его выводы делил минимум на 10. Мнение Cryptonist лично для меня более авторитетно.

Всем, у кого были проблемы с батареями Ledger nano X. Новая прошивка вроде решает вопрос:
https://m.youtube.com/watch?v=zb6uL3REsDw

Lixin, write when is it worth expecting the appearance of the Cyberpunk version of the wallet? Will it be multicurrency or bitcoin only version?

Don't be so nervous. By a compromised seed, I meant, for example, the operation of a random number generator built into the wallet, which can give out a far from random seed, but issue it according to an algorithm known by the manufacturer. In theory, the seed can be transferred byte-by-byte via QR codes. I'm not saying that Cobo or Keystone will do this on purpose. But people from criminal structures show interest in such companies and often try to introduce their own people there. Not one hardware wallet company is immune from this problem, just like any other financial company.

I do not mean that you will lose your seed. I am saying that your seed could theoretically be compromised on either the Cobo wallet or the Keystone wallet. Who in this case, in your opinion, will be to blame?

Let's say you decide to transfer your seed from Cobo wallet to Keystone wallet. let's hypothetically assume that after a while you have lost funds from your Keystone wallet. Who will you blame Cobo or Keystone? Are you 100% sure that Keystone is to blame? To avoid such incomprehensible situations, it is better to transfer your funds from Cobo to Keystone.

You start to manipulate. I didn't say Cobo or Keystone had bad intentions.
I wrote that Cobo and Keystone are completely different companies. And each of them must be responsible for its own generated seed. The fact that Lixin previously worked at Cobo does not mean that he can be responsible for the processes that are currently happening at Cobo. Likewise, Cobo should not be held responsible for Keystone processes.
Asking Lixin a question about transferring a seed from one wallet manufacturer to another manufacturer's wallet is forgivable for a beginner, but for a person who is well versed in cryptography, it can be understood as a provocation, hoping for his carelessness.
In addition, you registered your account 9 days after Lixin appeared here and immediately started with a negative, so it is highly likely that you are an employee from a competing company.
I am not against your constructive criticism of Keystone. But do not create deliberate provocations, and allow Keystone to develop normally.
Personally, I think that such wallets as Keystone and Ellipal are the most secure, although they are not very popular yet and must be present on the market.

I think you are well aware that Cobo and Keystone are now completely different companies. And giving advice to transfer the seed from a wallet of another manufacturer, which in theory could be deliberately compromised, on Keystone wallet surprises me. For the same reason, Cobo refused Keystone to sign the migration firmware for wallets with its logo, so as not to spoil its reputation in case of problems.
It surprises me even more that such a question is asked by a rather seriously knowledgeable user who, in the above question, describes the theoretical possibility of compromising private keys using signed transactions.
In addition to everything, you are new to this forum and for what purpose did you appear here and where you were before I do not understand?
All this leads to bad thoughts.
I also want to warn Lixin to be careful, not everyone is friendly on this forum, and every random word of yours can be used against you.

It's very good that you are showing the index for the change address! Trezor wallets don't show that. Ledger doesn't want to burden users with the problem of index spoofing at all.

I would like to advise you to add the following features to your wallets to differentiate you from your competitors for the better:

1. Many users do not trust the random number generators built into wallets, so it would be nice to let the user enter an arbitrary sequence of 0 and 1 (128 or 256) to form their own seed of 12 or 24 words.

2. Give an opportunity to import third-party cold private keys using: QR code, via SD card or virtual keyboard.
These features can only be added to the Pro model, which will significantly differ from the Essential model.

I hope you will listen to my advice and make a truly professional wallet that will significantly differ for the better from other wallets on the market.

I was just looking at buying a Keystone wallet. I really like the presence of a removable battery and also the absence of changing the addresses of coins, which makes it impossible to attack with the substitution of the address index:
https://blog.sia.tech/a-ransom-attack-on-hardware-wallets-534c075b3a92

I would like to see more popular coins available, such as ZEC.

Still wondering whether your servers are always available, do they have overloads? Is the commission calculated correctly?

Seed is encrypted in your wallet and shown to you only once. The only thing that the wallet can do is to compare your recorded seed with the saved one and report success or error.

Насколько я понял каких нибудь стандартных способов подключения Trezor к Bitcoin Core пока нет. Но по первой ссылке, котрый привел Witcher_sense показан пример подключения кошелька Coldcard к Bitcoin Core, используя Bitcoin Core API и подавая ему команды в формате JSON. Аналогично можно подключить и Trezor, но готового написаного решения от самих Trezor нет. В Trezor пишут, что у них уже есть ихнее готовое решение BlockBook (которое правда жрет много ресурсов) и других решений им не надо. Насчет "зуб дадите" я когдато прочитал в инструкции которая прилагалась к моему Trezor T, примерно следующее: "Вы покупаете в нашей компании только сам кошелек, но не покупаете програмное обеспечение и можете использовать любое на свой страх и риск". Вобщем зуб вам не даст даже Trezor за свое приложение Trezor suite.

Update:
Следующая версия Bitcoin Core V0.22 начнет поддержку аппаратных кошельков, с помощью подключения дополнительного скрипта подписей (External signer script)
https://github.com/bitcoin-core/gui/pull/4

Будут поддерживаться кошельки Ledger, Trezor, BitBox, KeepKey, ColdCard.
Более подробно какие модели будут поддерживаться и какие ихние функции будут доступны:
https://hwi.readthedocs.io/en/latest/devices/index.html#support-matrix

Ну лично я к Bitcoin Core Trezor не подключал, а рассматривал только вариант с установкой BlockBook.
Про Bitcoin core выше писал Witcher_sense:


Спросите лучше у него, возможно он гдето достал или сам написал соответствующее API.
Просто меня кроме Биткоина интересуют и другие монеты, поэтому вариант подключения к Bitcoin core я для себя не рассматривал, а больше интересовался BlockBook.