All - Activity - ryanRfox - Algorand

algosdk.error.AlgodHTTPError: broadcast queue full

It’s not clear to me if this is limited to Sandbox or all algod nodes. Here is an old Issue which references similar:

Please describe a bit more your method for sending transactions. Are you building/signing/sending one-at-time or batching?

The minimum balance requirements are composed of these parts:

  1. base (100,000 microAlgo per account)
  2. assets (100,000 microAlgo each)
  3. smart contract (varies based on state schema)
  4. box storage (varies based on bytes used)

Examples are provided within those links.

Have a look at ARC23 for “Appending application information to the compiled TEAL application”:
This uses a bytecblock to store additional information, but is NOT part of program execution. I’m not aware of TEAL programs that redefine the bytecblock during execution, as the reference algod compile …

The MetaDataHash field is optional and immutable at creation of the asset. It allows 32-bytes of arbitrary data storage.
A common use is for an NFT creator to hash the source digital asset and include the resulting value into MetaDataHash field. This makes it very easy for someone else to validate …

Please be advised that all official Algorand communications and software originate from the following sources:
Web
https://algorand.com (Algorand Inc.)
https://algorand.foundation (Algorand Foundation)
Twitter
@Algorand (Algorand Inc.)
@AlgoFoundation (Algorand Foundation)

Algorand addresses are encoded using base32 which is a standard 32-character set using the twenty-six upper-case letters A–Z and the digits 2–7. The digits 0,1,8 and 9 will not be found in any properly formed address.

A new tutorial may be of interest to you:
Create A Private Instance of Algorand In A Testbed
For example, this could be useful for researchers running stress tests on the Algorand network and measure metrics like scalability or resources utilization.

Yes, that looks like the proper process to rotate the auth-addr of acc_1 from acc_ms1 to acc_ms2. What have you attempted and where is it failing?

The agreement code defines the consensus implementation. The referenced README provides a good overview and some hints about where to dig for more within the code. Please let us know the level of detail you are seeking in your code exploration and where we can provide specific guidance. Below, is a …

127.0.1 is an invalid IP address format. Did you manually configure your config.json file? Take a look at (or set) the EndpointAddress value: "EndpointAddress": "127.0.0.1:8980"

Note: the format is host:port, so I suspect you have “127.0.1” for the host. When algod starts, it write the algod.net f…

Seems like a networking issue. Have a look in ~/node/data/node.log for some hints about what the node is doing at startup.

Yes, I can confirm the Algorand BSN Portal is functioning as expected now. @meowking following your testing and verification, please mark the reply @Haichao as resolved.

Yes, the manager address must be able to destroy ASA1 and ASA2 so that logic will be in there. The logic needs to include the ability to optin to each ASA prior to receiving them. This will cause some limitations if you go beyond issuing ASA1000 as you would need some other method to observe the man…

Yes, Step 4 generates the unsigned transaction file for you. Please confirm you successfully completed Steps 1-3. It seems odd you would get that open error in step 4 (unless you don’t have write access to create the file?). If you got Step 2 to work, I assume you have write access. That will create…

You’ll be applying a LogigSig as the signature for your opt-in transaction to/from the contract account (which is the logic that must pass to approve the transaction).

Yes, @rafmc98 have a look at this example HTLC Stateless Smart Contract for ASA.
Code overview
( (Scenario 1) OR ( ( Scenario 2 ) OR ( Scenario 3 ) ) AND Fee) ( ( Opt-in ) bnz ( ( Time Lock: ( ASA || Algos ) ) bnz ( Hash Lock: ASA Only ) ) && Fee )

Yes, please have a look at this tutorial to get you started from the command line.
If you are brand new to Algorand, you should use Sandbox to get running quickly:

I’m surprised Gitian was not discussed in this thread for trusted binaries using a deterministic build process. See also: What Is Gitian Building? How Bitcoin’s Security Processes Became a Model for the Open Source Community

Check out this Dev Portal Solution from @Pierce which details deploying an FDA Recalls Application using the Notes field to store the JSON results from the FDA API. Next, use the Indexer to query for recalls on products you may have already purchased. Please discuss below.

The 1000 rounds maximum you referenced is for the transaction validity period.
Have a look at this example for the renewal of participation keys showing 3M rounds per key:

Welcome @Prabhakaran258 glad you are here building!
Please have a look at these Windows instructions for requirements (git and docker), installation and usage:

Sandbox is now 2.0.
[Algorand Sandbox 2.0 Demo] @will wrote a great article introducing Sandbox 2.0 on the Developer Portal. Please have a read, download the bits, spin up your sandbox environment, and start building on Algorand.

Welcome @yfmao glad you are here building!
Have a look at this section of the docs for using the SDK to read global state:
Please let me know if that gets you closer. Please provide some of your code samples that are failing and we can troubleshoot further with you. Please use the triple tick t…

I re-read the OP. It seems you have the keyfile with your private key. You should be able to import that with another CLI Tool:
algokey import <keyfile>
That will also store your private key within kmd. You may then use goal to sign transactions.

Disclaimer: Never share you mnemonic phrase with anyone.
I’m not familiar with the coinomi app, nor how they generated the private key used to form your Algorand address. The following documentation describes the protocol for generating an Algorand address based based on BIP39 (24 words + 1 check…

Indexer is outside of the scope of this thread, so I’ll suggest you review the documentation provided

Yes, stop, start and then run the code block again.

Beginning 24 November, 2020 the Algorand Developer Relations Team will hold weekly Developer Office Hours to engage with the development community. Each week will feature a new topic with an overview demo provided prior to taking your development questions. Q&A is focused on building on Algorand wit…

Rock-Paper-Scissors anyone? This is the second in a series of tutorials using Reach to build DApps on Algorand. Give it a read:
[Blockchain Game Development for Algorand and Ethereum using Reach Lang == Rock Paper Scissors]
Let us know how it’s gong below…

Build it natively! No more emulators or even WSL, just build it from source using mingw64 on Windows 10 x64. Learn more by following this step-by-step tutorial:
Source code to synced in about 30 minutes! (depending on your build environment, use of Fast Catchup and network speed)
Please let us k…

From your latest screenshot, no, your node is not yet in sync. It was at round 759369. and mainnet is currently beyond 10362269 by now. When the node is in sync, the “Sync Time” will be 0.0 and the “Time since last block” value will be < 5 seconds.
I suggest you run that code block above to get a more…

Yes, I now see our documentation uses -d ~/node/datafastcatchup rather than -d ~/node/data as found elsewhere. It’s important to ensure the -d </path/to/data_folder> matches for both the goal node start and goal node catchup commands. Starting a node at one folder and then asking to catchup in a di…

@davidec did you attempt something similar to my process outlined in this PR within the sandobx GitHub repo? I’m keen to learn what you attempted and responses you received during testing.