# Galleon doesn't work

**URL:** <https://recherche.discourse.group/t/galleon-doesnt-work/266>\
**Category:** Galleon Support\
**Created:** [February 23, 2023, 7:09pm UTC](https://recherche.discourse.group/t/galleon-doesnt-work/266 "2023-02-23T19:09:12Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![662980](https://avatars.discourse-cdn.com/v4/letter/6/e79b87/32.png) [@662980](https://recherche.discourse.group/u/662980)\
**Post date:** [February 23, 2023, 7:09pm UTC](https://recherche.discourse.group/t/galleon-doesnt-work/266/1 "2023-02-23T19:09:12Z")

</div>

Any node, which you suggest, doesn’t work.

---

<div class="post-metadata">

**Author:** ![vishakh](https://yyz1.discourse-cdn.com/flex035/user_avatar/recherche.discourse.group/vishakh/32/202_2.png) [@vishakh](https://recherche.discourse.group/u/vishakh)\
**Post date:** [February 23, 2023, 7:59pm UTC](https://recherche.discourse.group/t/galleon-doesnt-work/266/2 "2023-02-23T19:59:36Z")

</div>

Please try now. We restarted some Tezos nodes.

---

<div class="post-metadata">

**Author:** ![662980](https://avatars.discourse-cdn.com/v4/letter/6/e79b87/32.png) [@662980](https://recherche.discourse.group/u/662980)\
**Post date:** [February 24, 2023, 4:50am UTC](https://recherche.discourse.group/t/galleon-doesnt-work/266/3 "2023-02-24T04:50:55Z")

</div>

Good, it’s working.  
😀

---

<div class="post-metadata">

**Author:** ![662980](https://avatars.discourse-cdn.com/v4/letter/6/e79b87/32.png) [@662980](https://recherche.discourse.group/u/662980)\
**Post date:** [February 24, 2023, 12:37pm UTC](https://recherche.discourse.group/t/galleon-doesnt-work/266/4 "2023-02-24T12:37:14Z")

</div>

Thank you. Now it is OK!  
What do you say about the future of Galleon Wallet? Will you support this Wallet in future? I ask you about it because now I have Galleon Wallet v. 1.3.5 (62), but the last version on your official site is 1.3.4???

чт, 23 февр. 2023 г. в 23:09, Vishakh via The Cryptonomic Discourse \<[notifications@cryptonomic.discoursemail.com](mailto:notifications@cryptonomic.discoursemail.com)\>:

---

<div class="post-metadata">

**Author:** ![vishakh](https://yyz1.discourse-cdn.com/flex035/user_avatar/recherche.discourse.group/vishakh/32/202_2.png) [@vishakh](https://recherche.discourse.group/u/vishakh)\
**Post date:** [February 27, 2023, 1:43pm UTC](https://recherche.discourse.group/t/galleon-doesnt-work/266/5 "2023-02-27T13:43:17Z")

</div>

We are actively working on a future direction for Galleon to ensure it is properly funded and resourced.

---

<div class="post-metadata">

**Author:** ![Jimmy](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@Jimmy](https://recherche.discourse.group/u/Jimmy)\
**Post date:** [February 17, 2024, 12:28pm UTC](https://recherche.discourse.group/t/galleon-doesnt-work/266/6 "2024-02-17T12:28:49Z")

</div>

@vishakh Presently, I cannot get access to my Tezos. Can someone from your team, please provide how to un delegate in Galleon. It should be just a case of providing how to do one command from looking into it.

Need to know how to run the contract command below within Galleon UI. I am in the unfortunate situation of not knowing my seed phrase, but I do know the password. So I can open the wallet in Galleon but cannot execute actions to un delegate. And as the Galleon wallet format is not supported in other wallets, I cannot import to those wallets.

I am also using the latest 1.4.1b and cannot see my KT1 contract but I do know its address.

As the KT1 is just a contract, we should be able to just call the KT1 contract address “do” function.

I found an example on the mainnet calling a KT1 do function and transferring tez out to the manager address. The below would have to be passed as a parameter into the contract call, with the address changed to the manager address.  
But I cannot work out how to pass it correctly as a parameter in the Galleon contract UI. I get an exception no matter what format I try.

The latest CALL in better call on the contract is all I need to do.

{ DROP ; NIL operation ; PUSH key\_hash “tz1Ln4x3HByGNpXHnrJpRtPj8CGVwfjFdaJE” ; IMPLICIT\_ACCOUNT ; PUSH mutez 8429870859 ; UNIT ; TRANSFER\_TOKENS ; CONS }

---

<div class="post-metadata">

**Author:** ![Jimmy](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@Jimmy](https://recherche.discourse.group/u/Jimmy)\
**Post date:** [February 17, 2024, 12:36pm UTC](https://recherche.discourse.group/t/galleon-doesnt-work/266/7 "2024-02-17T12:36:05Z")

</div>

@vishakh Even if I could get access to the source code, I could hard code in the contract address for the UI. Is that a possibility?

---

<div class="post-metadata">

**Author:** ![vishakh](https://yyz1.discourse-cdn.com/flex035/user_avatar/recherche.discourse.group/vishakh/32/202_2.png) [@vishakh](https://recherche.discourse.group/u/vishakh)\
**Post date:** [February 19, 2024, 11:38am UTC](https://recherche.discourse.group/t/galleon-doesnt-work/266/8 "2024-02-19T11:38:12Z")

</div>

@Jimmy If you would like to get this done within Galleon and you are comfortable sharing your Tezos address with us, please DM me your address.

If you would like to get it done in another wallet, please follow the instructions in [Migrating from Galleon to Another Tezos Wallet](https://discourse.cryptonomic.tech/t/migrating-from-galleon-to-another-tezos-wallet/378).

Let us know how it goes.
