Nope. The wallet never had anything to do with Gemini.
You must know it already but I noticed the following error after the Claim attempt:
[Aug 07, 2022, 11:13:24.7 AM:ERROR:credentials_promotion.cc(406)] UnBlindTokens: Unblinded creds size does not match signed creds sent in!
[Aug 07, 2022, 11:13:24.7 AM:ERROR:promotion.cc(515)] Credentials process not succeeded LEDGER_ERROR
It’s been repeating it at every run ever since.
was your wallet errored when attempting to claim at any time verified with Gemini?
No.
Dear @steeven
…the wallet is not verified…and I have several Brazilian friends who are having the same error…
thank you very much for your attention.
But I do have some verbose logs about this
@steeven
I put whatever I found was relevant
[ REQUEST ]
URL: https://grant.rewards.brave.com/v1/captchas
Method: POST
Content: {“paymentId”:“xyz{should I share}”}
Content Type: application/json; charset=utf-8
[07 Aug 2022, 1:14:55.0 am:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
Url: https://grant.rewards.brave.com/v1/captchas
Result: Success
HTTP Code: 200
Body: {“hint”:“square”,“captchaId”:“xyz{should I share}”}
[07 Aug 2022, 1:14:55.0 am:VERBOSE5:ledger_impl.cc(114)]
[ REQUEST ]
URL: https://grant.rewards.brave.com/v1/captchas/xyz{should I share}.png
Method: GET
[07 Aug 2022, 1:15:00.9 am:VERBOSE5:ledger_impl.cc(114)]
[ REQUEST ]
URL: https://grant.rewards.brave.com/v1/captchas/xyz{should I share}
Method: PUT
Content: {“solution”:{“x”:237,“y”:145}}
Content Type: application/json; charset=utf-8
[07 Aug 2022, 1:15:01.2 am:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
Url: https://grant.rewards.brave.com/v1/captchas/xyz{should I share}
Result: Failure
HTTP Code: 401
Body: {“message”:“: Error solving captcha”,“code”:401}
[07 Aug 2022, 1:15:01.2 am:ERROR:put_captcha.cc(55)] Invalid solution
[07 Aug 2022, 1:15:01.2 am:ERROR:attestation_desktop.cc(154)] Failed to confirm attestation
[07 Aug 2022, 1:15:01.2 am:ERROR:promotion.cc(366)] Attestation failed CAPTCHA_FAILED
[07 Aug 2022, 1:15:01.2 am:INFO:confirmations.cc(108)] Retry sending failed confirmations
[07 Aug 2022, 1:15:01.2 am:INFO:confirmations.cc(237)] Removed view confirmation for inline_content_ad with id xyz{should I share}, transaction id xyz{should I share} and creative instance id xyz{should I share} from the confirmations queue
[07 Aug 2022, 1:15:01.2 am:INFO:redeem_unblinded_token.cc(50)] Redeem unblinded token
[07 Aug 2022, 1:15:01.2 am:INFO:redeem_unblinded_token.cc(121)] FetchPaymentToken
[07 Aug 2022, 1:15:01.2 am:VERBOSE2:redeem_unblinded_token.cc(122)] GET /v2/confirmation/{confirmation_id}/paymentToken
[07 Aug 2022, 1:15:01.2 am:VERBOSE6:redeem_unblinded_token.cc(126)] URL Request:
URL: https://anonymous.ads.brave.com/v2/confirmation/xyz{should I share}/paymentToken
Method: kGet
[07 Aug 2022, 1:15:01.2 am:VERBOSE5:ledger_impl.cc(114)]
[ REQUEST ]
URL: https://grant.rewards.brave.com/v1/captchas
Method: POST
Content: {“paymentId”:“xyz{should I share}”}
Content Type: application/json; charset=utf-8
[07 Aug 2022, 1:15:02.0 am:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
Url: https://grant.rewards.brave.com/v1/captchas
Result: Success
HTTP Code: 200
Body: {“hint”:“circle”,“captchaId”:“xyz{should I share}”}
[07 Aug 2022, 1:15:02.0 am:VERBOSE5:ledger_impl.cc(114)]
[ REQUEST ]
URL: https://grant.rewards.brave.com/v1/captchas/xyz{should I share}.png
Method: GET
[07 Aug 2022, 1:15:02.4 am:INFO:redeem_unblinded_token.cc(137)] OnFetchPaymentToken
[07 Aug 2022, 1:15:02.4 am:VERBOSE6:redeem_unblinded_token.cc(139)] URL Response:
URL: https://anonymous.ads.brave.com/v2/confirmation/xyz{should I share}/paymentToken
Response Status Code: 200
[ REQUEST ]
URL: https://grant.rewards.brave.com/v1/captchas/xyz{should I share}
Method: PUT
Content: {“solution”:{“x”:221,“y”:133}}
Content Type: application/json; charset=utf-8
[07 Aug 2022, 1:15:10.4 am:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
Url: https://grant.rewards.brave.com/v1/captchas/xyz{should I share}
Result: Success
HTTP Code: 200
Body:
[07 Aug 2022, 1:15:10.4 am:INFO:database_creds_batch.cc(131)] Record size is not correct: 0
[07 Aug 2022, 1:15:10.4 am:VERBOSE5:ledger_impl.cc(114)]
[ REQUEST ]
URL: https://grant.rewards.brave.com/v1/promotions/xyz{should I share}
Method: POST
Content: {“blindedCreds”:[“xyz{should I share}”],“paymentId”:“xyz{should I share}”}
Content Type: application/json; charset=utf-8
Header digest: SHA-256=xyz{should I share
Header signature: keyId=“xyz{should I share}”,algorithm=“ed25519”,headers=“digest (request-target)”,signature=“xyz{should I share}==”
Header accept: application/json
[07 Aug 2022, 1:15:10.7 am:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
Url: https://grant.rewards.brave.com/v1/promotions/xyz{should I share}
Result: Success
HTTP Code: 200
Body: {“claimId”:“xyz{should I share}”}
[07 Aug 2022, 1:15:10.8 am:VERBOSE5:ledger_impl.cc(114)]
[ REQUEST ]
URL: https://grant.rewards.brave.com/v1/promotions/xyz{should I share}/claims/xyz{should I share}
Method: GET
[07 Aug 2022, 1:15:11.1 am:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
Url: https://grant.rewards.brave.com/v1/promotions/xyz{should I share}/claims/xyz{should I share}
Result: Success
HTTP Code: 200
Body: {“signedCreds”:[“xyz{should I share}”],“batchProof”:“xyz{should I share}”,“publicKey”:“xyz{should I share}”}
[07 Aug 2022, 1:15:11.1 am:ERROR:credentials_promotion.cc(406)] UnBlindTokens: Unblinded creds size does not match signed creds sent in!
[07 Aug 2022, 1:15:11.1 am:ERROR:promotion.cc(515)] Credentials process not succeeded LEDGER_ERROR
[07 Aug 2022, 1:15:11.1 am:INFO:promotion.cc(445)] Promotion completed with result LEDGER_ERROR
[07 Aug 2022, 1:15:11.5 am:INFO:confirmations.cc(108)] Retry sending failed confirmations
@steeven Also I don’t have verified wallet so cannot say
and I love this guy @Shayan786 how he puts xyz{should I share} everywhere not revealing a single id 
I think he asked if you ever tried to verify Gemini with your device in the past.
Try to put your entire code inside triple backticks like this:
``` YOUR CODE HERE ```
Me and my friend ( ~ 4 devices) still got this problem, after claim they said oop something is wrong then bat disapper with attested status ( not finished or active ) in brave://rewards-internals
wow check it out the payment status on the wallets says ‘‘paused’’ this is a first.I wonder whats going on and whats going to happen Geez seems serious
Let me guess…this issue will be fixed and people will get their bat next month. Right?
hey lets hope so, Ive never seen the payout status going from complete or available to being paused looks pretty serious but lets so what happens,hopefully it will be restored next month but the real question is whats really going on
For everyone here, if your claim amount shows Attested on brave://rewards-internals/ then you will get your Rewards eventually. Brave needs to make some tweaks that’s all.
Generally it is reflected automatically or you will have to claim again. Nothing to worry about.
how do you know? where did you here that?just asking
It comes from experience. 
hey lets hope so.do you have any idea why there are always problems with the brave rewards system like mAYBE it will run great for 2-3 months and a bug or something comes up and more changes and stuff like that like why are there always so many errors and stuff coz i can only think of two things but ill rather not share it but whats your opinion
Yeah, it’s difficult. And Brave has admitted that they try to patch a hole but somehow another one opens up. Trust me as it is difficult for users, it’s far more difficult for Brave everytime this happens.
Afterall a private payout mechanism for millions of users that has never been built before, is difficult to perfect.
I DM you with all details. I was waiting for 2 BATs to create account in Uphold and verify my wallet with it. Never created or used account at Gemini.
“Afterall a private payout mechanism for millions of users that has never been built before, is difficult to perfect.” I was just about to say that along with other issues, but hey lets see what happens
