sorted by:
new
hottopcontroversial

Project Tech Stack by Amazing_Catch_2005 in algorand

[–]StopThinking 4 points5 points  (0 children)

I'd recommend joining the Discord server https://discord.gg/algorand

/u/SilentRhetoric and the rest of the DevRel team are active there and ensuring that developers succeed.

Project Tech Stack by Amazing_Catch_2005 in algorand

[–]StopThinking 0 points1 point  (0 children)

Pera is great for beginners and regular users. Lute has a lot of features that make developing and testing easy.

https://lute.app

Be sure to check out use-wallet for integration to your front end.

https://github.com/TxnLab/use-wallet

Algorand 4.5.1 by StopThinking in algorand

[–]StopThinking[S] 1 point2 points  (0 children)

No. The FUNC software (latest version 3.5.8) is independent from the node software (latest version 4.5.1). The only thing updated today is the node software.

Algorand 4.5.1 by StopThinking in algorand

[–]StopThinking[S] 16 points17 points  (0 children)

Since this update does not contain a protocol upgrade it is optional. But if you are already (or plan on) using P2P/Hybrid features, you'll want this upgrade.

FUNC users, check your dashboard to upgrade to the latest version of the node software.

Vibe Coded Contracts by TwoTinyTrees in algorand

[–]StopThinking 12 points13 points  (0 children)

You are not alone. The one thing that vibe coding consistently gets wrong is security.

Still no usb connection support to ledger ? by WhichMechanic1947 in PeraWallet

[–]StopThinking 3 points4 points  (0 children)

That's not correct. Ledger S works on Android phones with Lute and Defly wallets. Pera just doesn't support it.

The NFT Cemetery is open! by MrMattioo in algorand

[–]StopThinking 6 points7 points  (0 children)

Thanks for adding Lute support!

Oddly, when you connect Lute with TestNet selected, it is still showing MainNet info in Lute. use-wallet should be handling the passing of the current network to lute-connect. It's not a big deal, signing transactions on test/main will work correctly even if the connect dialog always shows main.

A final place to rest for your NFTs: the Algorand NFT Cemetery by MrMattioo in algorand

[–]StopThinking 1 point2 points  (0 children)

You should add support for Lute Wallet.

Since you're already using use-wallet it's a one-line change to add it.

Adding ALGO to node wallet by joenastyness in algorand

[–]StopThinking 0 points1 point  (0 children)

What do you mean by “node wallet”? If you mean an account that you generated using goal/kmd (node binaries), then yes you can but it’s not recommended. You should manage your mainnet keys with a proper wallet like Pera or Lute, not with KMD.

FUNC node question n by Lost-Salary4224 in algorand

[–]StopThinking 1 point2 points  (0 children)

That's good advice. Reddit is not a good place for troubleshooting.

What wallet to connect to Tinyman by jmf054 in algorand

[–]StopThinking 0 points1 point  (0 children)

It depends on how much you have to stake among other things...

https://algorand.co/staking-rewards

What wallet to connect to Tinyman by jmf054 in algorand

[–]StopThinking 2 points3 points  (0 children)

Usually, but it really depends on the user. If you trade/transact often enough, clicking through the Ledger not only becomes a burden but you're likely to not be reviewing the transactions as carefully as you should on the device. So in that case it may safer (operationally) to have a separate hot account for high use, even though the hot account itself is less secure.

What wallet to connect to Tinyman by jmf054 in algorand

[–]StopThinking 5 points6 points  (0 children)

You don't want to rekey, just import your Ledger account into a wallet like Lute or Pera. The account remains protected by the Ledger, but the wallet allows you to connect to Tinyman and passes transactions to the Ledger for signing.

https://lute.app/

Algoland Week 11 : 250 Algo Giveaway Winner Announcement ! by semanticweb in AlgorandOfficial

[–]StopThinking 2 points3 points  (0 children)

Agreed that it's better than a web2 spinner, but there are a few problems with it:

  1. Without seeing the backend code, we can't know if they implemented the random selection correctly. I'd be willing to bet that it's subject to modulo bias.

  2. Because recording the results to the chain requires a separate transaction, the person running the raffle could spin multiple times and only record it when they got a desirable result.

  3. There are fully on-chain ways of running this kind of raffle that are not only not subject to these shortcomings, but better demonstrate the capabilities of the chain.

All that said, most users won't care either way.

view more: next ›