Smart Tool Explorer

[Lucretia]

Aftera smart contract is deployed, the Theta explorer allows users to upload and verify the source code of the smart contract. To do this, after a smart contract is deployed on chain, navigate to the explorer page for the contract address. Then simply scroll down the page. After the "Transactions" section, you should see a text box for uploading the contract source code. Simply copy and past your contract source code, and select the Compiler Version and Optimization option (need to be identical to your settings when you compiled the contract). Next hit "Verify and Publish".

Similar to Etherscan, the Theta Explorer can display the event logs emitted by smart contract execution for the DApp developers to inspect the internal state of the smart contracts. First, navigate to a transaction which executes a smart contract function. The example below shows the detail page for a transaction that calls the setValue() function of the above SquareCalculator contract. The "Overview" tab displays some general information including the Gas Used and the Gas Price.

Users are now able to verify and manage their smart contracts directly through the Avalanche Explorer. Smart contract verification allows users to access and verify the source code, promoting user confidence in the functionality of the smart contracts they engage with. Meanwhile, submitting info about the smart contract enables contract owners to provide essential details, fostering trust and transparency.

Previously deployed smart contracts will be displayed here. Contracts already verified will have a green icon. This tutorial will look at how to verify and edit the information provided for smart contracts.

NOTE: Avalanche uses Sourcify to compile and verify contracts behind the scenes. A verified contract does not certify the security, performance, or integrity of the smart contract. Nor is it an endorsement of the contract or its owner.

NOTE: Editing contract information is only available for previously verified contracts deployed by the currently connected wallet. If the contract has not been verified yet, please perform the listed steps above.

These are two separate tools with different verification mechanisms.

To verify on subnets.avax.network, users can either go to and verify their contract. Alternatively, to verify a contract using hardhat on subnets.avax.network they can reference the following document.

MultiversX Explorer offers web-based interfaces where users and developers can query and inspect details of transactions, blocks, smart contracts, addresses, and various on-chain activities. These explorers are essential tools for transparency, auditing, and debugging purposes in blockchain ecosystems. It offers a GUI for interacting with smart contracts directly from the browser.

At HiveMQ we have worked with many customers to develop and test their MQTT deployments. One thing we have found is the need for a command line tool to quickly generate MQTT test clients to test the connections between clients and an MQTT broker. Over the years, we have used various utilities developed by the open source community but none seem to have all the features we needed.

For this reason, we are happy to announce a new open source tool, called MQTT CLI, that provides a command line interface (CLI) to interact with an MQTT broker. The new tool provides two key features: 1) a SHELL mode that allows you to start multiple MQTT clients in parallel and supports connection handling and provides unix-like shell features, such as color-highlighting, tab-completion, command-history, and password masking. 2) support for both MQTT pub and sub commands so you have one command line for all the key MQTT operations.

We are making the MQTT CLI available in open source under the Apache License 2.0. The tool supports MQTT 3.1.1 and MQTT 5 and can be used with any MQTT broker. Our hope is to see this tool being embraced by the entire MQTT community, not just HiveMQ users. We have tested it with the HiveMQ public broker and the Mosquitto public broker. Feel free to try it out and let us know what you think.

The MQTT CLI is an open-source Java MQTT client tool that enables you to interact quickly and easily with any MQTT Broker in various ways. The CLI gives you a single compact tool for the most important client operations (PUBLISH and SUBSCRIBE). The CLI tool also provides an interactive and comfortable SHELL mode that enables you to work with multiple MQTT clients in parallel and supports connection handling. The MQTT CLI supports all MQTT features for MQTT Version 5 & 3.1.1. The tool uses the HiveMQ-MQTT client library, which is a fast, low-overhead, high-throughput, and modern MQTT library written in Java.The MQTT CLI comes in various binary packages that can be downloaded from the documentation homepage on GitHub.

If you are using a *nix operating system which operates with debian packages you can download the MQTT CLI debian package from the releases page here via wget or curl and install the package with:

sudo dpkg -i

or

sudo apt install.

For Red Hat, Fedora, Mandriva, OpenSuse, CentOS distributions you can use the rpm package provided at releases page here. The preferred way is to install the package via the yum package manager. To install the package simply execute:

The shell mode gives you a client context for the MQTT clients that are currently connected. You can connect MQTT clients, work with the clients to publish, subscribe, unsubscribe, or list all clients to disconnect all or a few of your MQTT clients. Methods such as Connect and Disconnect switch the current context of the shell. Commands such as Publish and Subscribe always relate to the client context that is currently active.

The MQTT CLI works with a default configuration of commonly used values. The first time the CLI successfully executes, the default configuration file is generated and stored in the .mqtt-cli/ subfolder of your home folder.

The VERBOSE logging mode provides detailed and fine grained information about each operation, MQTT message, and acknowledgement. Additionally, any errors that occur are logged with a full stack trace.

The MQTT CLI is an open source project under Apache 2 license and hosted by HiveMQ. With the MQTT CLI you have a smart and compact tool that helps you especially during the development and test phase, to easily and quickly execute MQTT operations at the command line level. Distributions for the most common operating systems are available. Try out our smart tool and download from Github.

Anja Helmbrecht-Schaar was previously a Senior MQTT & Architectural Consultant at HiveMQ. Anja supported customers with the application-specific implementation of HiveMQ extensions as well as the introduction and integration of HiveMQ into their system landscape. She is an MQTT expert who has held many workshops around the protocol and the HieMQ broker.

OpenSC offers the standard distribution as well as a light weight distribution. The light weight variant is compiled without external dependencies (such as OpenSSL or zlib) and has a limited set of card drivers and smart card tools.

Upon successful installation the 32 bit (and 64 bit) minidriver have successfully been registered with their registry keys in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Calais\SmartCards (the 32 bit keys on an 64 bit OS are available in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Wow6432Node\Cryptography\Calais\SmartCards).

Change the default configuration file C:\Program Files\OpenSC Project\OpenSC\opensc.conf to your needs. The configuration options are explained within this file. For 32 bit applications on an 64 bit OS you need to also edit C:\Program Files (x86)\OpenSC Project\OpenSC\tools\opensc.conf.

Open the Control Panel and click on the Uninstall a program option under the Programs category. If you are using the Classic View of the Control Panel, then double-click on the Programs and Features icon instead. From the list of installed programs, choose OpenSC smartcard framework and click Uninstall. Do the same for OpenSC smartcard framework (64bit).

It is possible that a background process locks the minidriver library though uninstalling is successful. Remove C:\Windows\System32\opensc-minidriver.dll and C:\Windows\SysWOW64\opensc-minidriver.dll manually if required.

Yesterday I was working with a file that contained several smart objects on my 2017 MacBook Pro (16gb). I noticed that doing simple things like press cmd-plus or minus to zoom in or out, using the grab tool to pan around, and click visibility of layers on or off would be met with a delay of a second or two. If I switched to a tab with a file that had very few or no smart objects (about the same size or larger) the delay would disappear. I assumed that the problem was with some settings, so I messed with some performance settings and I thought it helped for a while, but then the problem came back.

There are so many variables involved in this.

You mentioned having multiple documents open, and you could also have multiple applications open, you might not have the recommended 8GB of RAM, you might not have much hard disk space, your computer is old so might be running slowly, and the smart objects could be huge bitmaps, and smart objects retain the actual file size so the files could be really large. Lots of different factors here.

Mark, as I mentioned, this is happening on two completely different computers. One is a fairly new MacBook Pro with 16GB of ram and a good sized ssd drive with plenty of space on it. The other is an older Mac Pro, but it's got 64 GB ram. These files are not huge files. And I don't have a lot of other apps open.

Hey there, yes something is up with the more recent versions of Photoshop CC, or you are hitting the roof of the capabilities. What has happened to me with recent updates and was previously not a problem, is a file that has around 70 layers in it of 60px icons for a website that I use to drop in and colour etc, has been fine fine fine adding to it and it has grown over time then adding in one layer now and Photoshop just grinds to a complete halt, it's only using 10% CPU, has 30+ GB of Ram available, is using a GTX1060 + 8700K i7 3.70GHz machine, it's fast and does most everything instantly - NVME scratch disk and lots of ram applied to it too. Windows obviously - but I feel I have reached the cap of the ability of Photoshop to handle smart objects at around the 60 mark, not all layers are smart objects, I have had to break the one file up to three groups of 25 layers now so I can work on it. Even the mouse skips and jumps when I am going over the page, but I can swap out to any other app and it's working fine, ram usage is 2GB and CPU no more than 10 at peak, go back to photoshop and nothing changes but the computer just seems to lag like it's maxed out in every respect. Mouse lags, stops, clicks take a minute to register, then happen all at once etc. It's horrendous. So I would say we both have pushed things beyond Photoshops capabilities. It needs to be fixed.

3a8082e126