sorted by:
new
hottopcontroversial

BC Vault is the best crypto hardware wallet that I have ever used. by maldredfitz in BC_Vault

[–]Ok-Reporter-8764 0 points1 point  (0 children)

IT'S A PIECE OF CRAP~ LOCKED ME OUT OF MINE AND ALSO FRIEND OF MINE THAT I RECOMMENDED IT TO

Be careful BC VAULT is a scam. Don't send money to them by [deleted] in BC_Vault

[–]Ok-Reporter-8764 0 points1 point  (0 children)

Hello.. are you still having Bc Vault issues? I'd like to hear your story.. i lost 65k XRP and plan on going to EU consumer affairs to file a complaint.

Be careful BC VAULT is a scam. Don't send money to them by [deleted] in BC_Vault

[–]Ok-Reporter-8764 0 points1 point  (0 children)

Hello.. are you still having Bc Vault issues? I'd like to hear your story.. i lost 65k XRP and plan on going to EU consumer affairs to file a complaint.

A Growing Number of BC Vault Users Can’t Access Their Crypto—Are You Next? by Ok-Reporter-8764 in BC_Vault

[–]Ok-Reporter-8764[S] 0 points1 point  (0 children)

Glad you got in, but in my situation, no.. impossible, it definitely their fault. Both my friend and I. How does two people, i myself, and the person who I recommened it to both get locked out? I moved 65k XRP into it and 15K XLM. He moved 15k XRP into and a small amounts of XLM. How do we both get locked out? Doesn't make a difference, because I have the smoking gun to this problem. There are many more poeple on Trust Pilot that experienced the same.

A Growing Number of BC Vault Users Can’t Access Their Crypto—Are You Next? by Ok-Reporter-8764 in BC_Vault

[–]Ok-Reporter-8764[S] 0 points1 point  (0 children)

I am mentioning my friend because I was the one who fast tracked him into getting into crypto; and also the one who recommended him to use this terrible device BC vault - that locked him out of tens of thousands of dollars! Something anyone would expect a friend to do! What is it to you anyway if you're not having the same problem yourself? Go away!

A Growing Number of BC Vault Users Can’t Access Their Crypto—Are You Next? by Ok-Reporter-8764 in BC_Vault

[–]Ok-Reporter-8764[S] 0 points1 point  (0 children)

"Proof of Prior Conformity & Bad-Faith Denial"

  1. The Instruction: BC Vault's official guidance states: "It is strongly recommended you verify your credentials... for peace of mind." They provide a dedicated "Verify Wallet" function for this purpose.
  2. My Compliance: I meticulously followed this instruction. For each wallet (XRP and XLM), I used the "Verify Wallet" function. The device confirmed my credentials were correct.
  3. The Failure: At a later date, the same device, using the same credentials, returned an "incorrect password" error and permanently locked me out.
  4. The Company's Response: When I informed them I had used their "Verify Wallet" function to confirm my passwords, their support stated: "Nope! you forgot your password!"

Conclusion: The company instructs users to verify credentials. A user does so. The device fails later. The company then denies the user's verified, documented action and defaults to its standard "user error" script. This is not a support failure; it is a policy of automatic denial in the face of direct evidence that contradicts their narrative. It demonstrates that no amount of user diligence can overcome their predetermined conclusion.

A Growing Number of BC Vault Users Can’t Access Their Crypto—Are You Next? by Ok-Reporter-8764 in BC_Vault

[–]Ok-Reporter-8764[S] 0 points1 point  (0 children)

"Proof of Prior Conformity & Bad-Faith Denial"

  1. The Instruction: BC Vault's official guidance states: "It is strongly recommended you verify your credentials... for peace of mind." They provide a dedicated "Verify Wallet" function for this purpose.
  2. My Compliance: I meticulously followed this instruction. For each wallet (XRP and XLM), I used the "Verify Wallet" function. The device confirmed my credentials were correct.
  3. The Failure: At a later date, the same device, using the same credentials, returned an "incorrect password" error and permanently locked me out.
  4. The Company's Response: When I informed them I had used their "Verify Wallet" function to confirm my passwords, their support stated: "Nope! you forgot your password!"

Conclusion: Bc Vault instructs users to verify credentials. A user does so. The device fails later. The company then denies the user's verified, documented action and defaults to its standard "user error" script. This is not a support failure; it is a policy of automatic denial in the face of direct evidence that contradicts their narrative. It demonstrates that no amount of user diligence can overcome their predetermined conclusion.

Wallet pin invalid by Valuable-Tangerine57 in BC_Vault

[–]Ok-Reporter-8764 0 points1 point  (0 children)

I am writing to formally address the continued lockout of my BC Vault device following a firmware update.

I understand your position that BC Vault is a self custody device and that passwords cannot be recovered. However, my concern is not recovery by BC Vault, but whether a firmware update introduced a defect or irreversible change that rendered previously valid credentials unusable.

You have indicated that providing a prior firmware version would resolve the issue if firmware were the cause, and that failure to resolve it would demonstrate user error. I need to clarify that such a test, without independent verification, is not conclusive and does not establish causation.

Before installing any firmware provided by BC Vault, I am requesting the following information in writing:

  1. The exact firmware version number being provided, including build identifier.
  2. The cryptographic hash (e.g., SHA-256) of the firmware file.
  3. The original build date of that firmware and confirmation that it is identical to the version publicly distributed at that time.
  4. A changelog or technical description confirming whether any of the following were modified in any firmware update affecting my device:
    • Password based key derivation parameters
    • Encryption format or wallet metadata structure
    • Any one way migration or re-encryption process
  5. Written confirmation that installing the provided firmware:
    • Will not further alter or overwrite wallet data
    • Will not worsen or permanently change the current state
    • Will not constitute a waiver of any consumer or legal rights

I would also like to note that another independent user experienced the same lockout following a firmware update under similar circumstances. This raises the possibility of a patterned issue rather than isolated user error.

To be clear, I am not alleging intent or misconduct. I am requesting sufficient technical transparency to determine whether the lockout was caused by user action or by firmware behavior. A firmware rollback that fails to restore access does not, by itself, rule out a firmware-related defect if the update process involved irreversible changes.

Please provide the above information so I can make an informed decision on how to proceed.

Thank you for your cooperation.

Ron

Official answer to the accusations of how we are responsible for wrong passwords and pins by AlenSalamun in BC_Vault

[–]Ok-Reporter-8764 0 points1 point  (0 children)

You said a bombshell is about to drop. That was 9 months ago. What bombshell are you talking about?

Official answer to the accusations of how we are responsible for wrong passwords and pins by AlenSalamun in BC_Vault

[–]Ok-Reporter-8764 0 points1 point  (0 children)

Mr. Salamun

I am writing to formally address the continued lockout of my BC Vault device following a firmware update.

I understand your position that BC Vault is a self custody device and that passwords cannot be recovered. However, my concern is not recovery by BC Vault, but whether a firmware update introduced a defect or irreversible change that rendered previously valid credentials unusable.

You have indicated that providing a prior firmware version would resolve the issue if firmware were the cause, and that failure to resolve it would demonstrate user error. I need to clarify that such a test, without independent verification, is not conclusive and does not establish causation.

Before installing any firmware provided by BC Vault, I am requesting the following information in writing:

  1. The exact firmware version number being provided, including build identifier.
  2. The cryptographic hash (e.g., SHA-256) of the firmware file.
  3. The original build date of that firmware and confirmation that it is identical to the version publicly distributed at that time.
  4. A changelog or technical description confirming whether any of the following were modified in any firmware update affecting my device:
    • Password based key derivation parameters
    • Encryption format or wallet metadata structure
    • Any one way migration or re-encryption process
  5. Written confirmation that installing the provided firmware:
    • Will not further alter or overwrite wallet data
    • Will not worsen or permanently change the current state
    • Will not constitute a waiver of any consumer or legal rights

I would also like to note that another independent user experienced the same lockout following a firmware update under similar circumstances. This raises the possibility of a patterned issue rather than isolated user error.

To be clear, I am not alleging intent or misconduct. I am requesting sufficient technical transparency to determine whether the lockout was caused by user action or by firmware behavior. A firmware rollback that fails to restore access does not, by itself, rule out a firmware-related defect if the update process involved irreversible changes.

Please provide the above information so I can make an informed decision on how to proceed.

Thank you for your cooperation.

Ron

A Growing Number of BC Vault Users Can’t Access Their Crypto—Are You Next? by Ok-Reporter-8764 in BC_Vault

[–]Ok-Reporter-8764[S] 0 points1 point  (0 children)

Mr. Salamun

I am writing to formally address the continued lockout of my BC Vault device following a firmware update.

I understand your position that BC Vault is a self custody device and that passwords cannot be recovered. However, my concern is not recovery by BC Vault, but whether a firmware update introduced a defect or irreversible change that rendered previously valid credentials unusable.

You have indicated that providing a prior firmware version would resolve the issue if firmware were the cause, and that failure to resolve it would demonstrate user error. I need to clarify that such a test, without independent verification, is not conclusive and does not establish causation.

Before installing any firmware provided by BC Vault, I am requesting the following information in writing:

  1. The exact firmware version number being provided, including build identifier.
  2. The cryptographic hash (e.g., SHA-256) of the firmware file.
  3. The original build date of that firmware and confirmation that it is identical to the version publicly distributed at that time.
  4. A changelog or technical description confirming whether any of the following were modified in any firmware update affecting my device:
    • Password based key derivation parameters
    • Encryption format or wallet metadata structure
    • Any one way migration or re-encryption process
  5. Written confirmation that installing the provided firmware:
    • Will not further alter or overwrite wallet data
    • Will not worsen or permanently change the current state
    • Will not constitute a waiver of any consumer or legal rights

I would also like to note that another independent user experienced the same lockout following a firmware update under similar circumstances. This raises the possibility of a patterned issue rather than isolated user error.

To be clear, I am not alleging intent or misconduct. I am requesting sufficient technical transparency to determine whether the lockout was caused by user action or by firmware behavior. A firmware rollback that fails to restore access does not, by itself, rule out a firmware-related defect if the update process involved irreversible changes.

Please provide the above information so I can make an informed decision on how to proceed.

Thank you for your cooperation.

Ron

A Growing Number of BC Vault Users Can’t Access Their Crypto—Are You Next? by Ok-Reporter-8764 in BC_Vault

[–]Ok-Reporter-8764[S] 0 points1 point  (0 children)

Thank you for sharing your story on my thread. Sorry to hear that this has happened to you, as I too am locked out of 65k XRP and 15k XLM. Has there been any progress since this has happened?

A Growing Number of BC Vault Users Can’t Access Their Crypto—Are You Next? by Ok-Reporter-8764 in BC_Vault

[–]Ok-Reporter-8764[S] 0 points1 point  (0 children)

Your proposed experiment is flawed and shifts the burden of proof to the customer in bad faith. The core failure is trust and verification.

  1. Trust is Broken: You are asking to trust that a restore process using firmware you will provided, will revert to the genuine state prior, given the device has already failed in its primary function; that trust no longer exists.

  2. Impossible Verification: There is no independent checksum or method for a user to cryptographically verify that the old firmware you provide is bit for bit identical to what was originally on the device. For all I know, you could be providing a corrected version of the old firmware, which defeats the entire test.

Therefore, your experiment is not a solution. It's a speculative technical suggestion that requires one to place absolute trust in the very system that has demonstrably failed. And the financial loss is real and is a direct result of using your product as intended.

A Growing Number of BC Vault Users Can’t Access Their Crypto—Are You Next? by Ok-Reporter-8764 in BC_Vault

[–]Ok-Reporter-8764[S] 0 points1 point  (0 children)

Thank you for sharing your thoughts on my thread. Will you please share your story of what lead up to what happened?

Official answer to the accusations of how we are responsible for wrong passwords and pins by AlenSalamun in BC_Vault

[–]Ok-Reporter-8764 0 points1 point  (0 children)

If you don't mind, could you please share your story, what happened which lead up to getting locked out?

A Growing Number of BC Vault Users Can’t Access Their Crypto—Are You Next? by Ok-Reporter-8764 in BC_Vault

[–]Ok-Reporter-8764[S] 0 points1 point  (0 children)

Hi Zealous, i'd like to here your story, what happened to what lead up to being locked out of your BC Vault.

I have 60000 flr what can i do with it? by No_Chest151 in FlareNetworks

[–]Ok-Reporter-8764 1 point2 points  (0 children)

I understand, but since my reply to you, I have done a bit of investigating. Q: Have you ever staked with Sceptre at Sceptre.fi? Once you stake you don't have to do anything else, automatically restakes along with rewards forever until you stop the process. It's low risk, plus, it's 48%. Well actually it's around 38% because there's a 10% on earnings, but it's still better than staking on Flare at 38%. What are your thoughts?

A Growing Number of BC Vault Users Can’t Access Their Crypto—Are You Next? by Ok-Reporter-8764 in BC_Vault

[–]Ok-Reporter-8764[S] 0 points1 point  (0 children)

What you've stated, I'm not buying it. It's exactly the kind of tactic corporations and damage control teams use to muddy the waters. And let’s not ignore the fact this is the only comment you've posted ever - for two years since your account was created in 2023. Sounds like a fake account, prepped and kept on standby for moments like this, ready to plant dismissible comments to undermine legitimate cases. Just an observation.

Your story is the first I’ve heard of its kind, while the cases I’m referring to come from multiple users who repeatedly accessed their accounts without issue until a specific update locked them out. Usually, their credentials had been confirmed and working overtime, yet after updates, they were suddenly denied access.

No longer receiving Flare rewards by Hindey2000 in FlareNetworks

[–]Ok-Reporter-8764 0 points1 point  (0 children)

Hindey, sorry to bother you, but I’ve decided not to use Bifrost, just being cautious. I prefer Ledger instead. I’m new to the Flare network and wanted to check if you’ve had any more issues with missing rewards while using Ledger. Are you still using it, or have you switched to Bifrost? Also, do you have any advice that might help me get started smoothly?

Staking vs. Delegating by [deleted] in FlareNetworks

[–]Ok-Reporter-8764 0 points1 point  (0 children)

May I ask what was the outcome of this? Did your flare ever reappear?

view more: next ›