Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 21:22
    kclowes edited #1778
  • 21:22
    kclowes synchronize #1778
  • 20:17
    tmckenzie51 synchronize #1780
  • 20:08
    tmckenzie51 synchronize #1780
  • 19:50
    tmckenzie51 synchronize #1780
  • 19:20
    tmckenzie51 synchronize #1780
  • 18:51
    tmckenzie51 synchronize #1780
  • 18:26
    marcgarreau commented #1585
  • 17:27
    marcgarreau synchronize #1585
  • 16:55
    marcgarreau synchronize #1585
  • 11:25
    sobolev-igor opened #1781
  • Oct 23 22:46
    kclowes synchronize #1778
  • Oct 23 22:15
    tmckenzie51 synchronize #1780
  • Oct 23 22:11
    tmckenzie51 opened #1780
  • Oct 23 16:49
    Pet3ris closed #1779
  • Oct 23 16:49
    Pet3ris commented #1779
  • Oct 23 15:48
    kclowes commented #1585
  • Oct 23 14:19
    marcgarreau edited #1585
  • Oct 23 14:19
    marcgarreau commented #1585
  • Oct 23 14:19
    marcgarreau commented #1585
Mikko Ohtamaa
@miohtama
go back to 100
because there are time periods when you get a lot of events and time periods when you get less events
brschkv
@brschkv
but still, the same query as above works perfectly fine with web3.js all the way back to block 0
in one shot
Mikko Ohtamaa
@miohtama
ah
@brschkv I think the best way to debug - would be try to run your own node and test against it
so you get more visibility what is going on on the node side
maybe there is a difference how web3.py and web3.js construct the query
so you could also sniff that from HTTP traffic
brschkv
@brschkv
Yes, that is what the infura support hinted in the issue linked above. I have not looked into the code yet, but would be willing to help fixing this.
There are some things, that web3.js still does better. And it annoys me personally because I like web3.py a lot better and would like to use it exclusively. But I constantly have to jump back to web3.js for certain tasks... :-(

@brschkv I think the best way to debug - would be try to run your own node and test against it

I don't have the infrastructure at hand to do that unfortunately...

maybe there is a difference how web3.py and web3.js construct the query

I hope I can make some time to look into that later.

brschkv
@brschkv
There's also an open issue for this already: ethereum/web3.py#1523
Nick Mudge
@mudgen
Mikko Ohtamaa
@miohtama
@mudgen The standard seems to propose a more complicate upgrade proxy. I read through quickly, but not really understand what's the unique selling point here.
good to know, thank you!
Ed Noepel
@EdNoepel
Nick/Piper: I believe I resolved concerns with ethereum/web3.py#1620 three weeks back. What's the process for getting this merged and into a release? Thanks in advance.
Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<carver> @Piper I don't have any context on this, is this good to go? ^
Nick Mudge
@mudgen
@miohtama Thanks for taking a look. @miohtama One of the big selling points is that it solves the 24KB max size contract limit. Another thing it does is provide a simpler way to handle complex contract interaction.
@miohtama The Diamond Standard is a more complicated upgrade proxy but it is a simpler way to handle larger sets of contracts that need to interact with each other.
A new Python tool was released today for automating the upgrade process of Ethereum Diamonds: http://joeyzacherl.com/2020/06/diamond-setter-ethereum-smart-contract-manager/
Mikko Ohtamaa
@miohtama
Nice!
Though in practice it cannot be a single command, as most of the critical contracts are managed by multisigs or DAOs :)
Manuel Montenegro
@manumonti

Hi, I have a problem sending a raw transaction. I'm following the example in documentation, but Python returns an error. I'm not sure if it's a bug or just I'm doing it in the wrong way.

I have deployed a Hyperledger Besu network. So I'm using Web3 middleware. And I want to send a transaction using local keys. I can make the transaction using Metamask, so I think Besu network is not the problem.

Well, I first sign the transaction using the key of an account, after i send the signed transaction and by last I wait for transaction receipt. Here is the code:

w3 = Web3(Web3.HTTPProvider("http://192.168.43.125:10101"))
w3.middleware_onion.inject(geth_poa_middleware, layer=0)
accountKey = '0x...'
transaction = {
    'to': '0x...',
    'value': w3.toWei(0, 'ether'),
    'gas': 2000000,
    'gasPrice': 100,
    'nonce': 0,
    'chainId': 5403
}
signed = w3.eth.account.sign_transaction(transaction, accountKey)
txHash = w3.eth.sendRawTransaction(signed.rawTransaction)
txReceipt = w3.eth.waitForTransactionReceipt(txHash)

And here is the weird thing: I can run this python3 script once! (and it works as expected). But the second time I run, I get this error:

Manuel Montenegro
@manumonti
Ok, forget it. This is the answer if someone has a similar problem: I forgot to manage the nonce number of the transaction... I always send a nonce = 0
Mikko Ohtamaa
@miohtama
@manumonti the most efficient way to share information like this is to open a question on ethereum.stackexchange.com and then answer your question yourself.
ethereum.stackexchange.com is very searcahble and answers also rank high in Google
francocoin1701
@francocoin1701
hello everyone I am a developer a long time ago but I started this year with all this block-chain I would like to learn more about web 3 but I cannot install the library with pip this is my mistake:
Building wheels for collected packages: lru-dict, cytoolz, bitarray
Building wheel for lru-dict (setup.py): started
Building wheel for lru-dict (setup.py): finished with status 'error'
Running setup.py clean for lru-dict
Building wheel for cytoolz (setup.py): started
Building wheel for cytoolz (setup.py): finished with status 'error'
Running setup.py clean for cytoolz
Building wheel for bitarray (setup.py): started
Building wheel for bitarray (setup.py): finished with status 'error'
Running setup.py clean for bitarray
Failed to build lru-dict cytoolz bitarray
Installing collected packages: lru-dict, cytoolz, eth-utils, eth-keys, eth-keyfile, bitarray, rlp, parsimonious, eth-abi, eth-rlp, eth-account, websockets, web3
Running setup.py install for lru-dict: started
Running setup.py install for lru-dict: finished with status 'error'
someone that want help me please..
Marc Garreau
@marcgarreau
@francocoin1701 there is some documentation for getting a clean environment set up: https://web3py.readthedocs.io/en/stable/troubleshooting.html#setup-environment
Ajmal Hassan
@iamajmalhassan
Hello Everyone,
how do you find the account number given the private key in web.py?
arjuna sky kok
@arjunaskykok_gitlab
from eth_keys.backends.native.ecdsa import private_key_to_public_key
from eth_keys.utils.address import public_key_bytes_to_address
from eth_utils import to_normalized_address

public_key = private_key_to_public_key(private_key)
address = public_key_bytes_to_address(public_key)
normalized_address = to_normalized_address(address)
Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<Piper> I just realized we should look into extending our integration tests to cover ganache
<carver> To get an address from a private key in two lines ^
Voith Mascarenhas
@voith

I just realized we should look into extending our integration tests to cover ganache

Been a while since I contributed to web3.py. I’d like to take this up. I’m quite familiar with the integration test-suite and I have some free time this weekend.
@marcgarreau Is there an issue for this?

Marc Garreau
@marcgarreau
@voith thanks for jumping back in! no issue yet, feel free to create one if you want to solicit more thoughts from the team.
Marc Garreau
@marcgarreau

web3.py 5.11.1 released :rocket:

This includes a ton of type annotation fixes and some beefing up of the intro docs. Thanks to @Uxio0 and @MatthiasLohr for contributions this round :clap:

https://web3py.readthedocs.io/en/stable/releases.html#v5-11-1-2020-06-17

Mikko Ohtamaa
@miohtama
@marcgarreau @MatthiasLohr excellent work, thank you sirs
Marc Garreau
@marcgarreau
and thank you @miohtama for helping to answer questions around here :smile:
Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<Christoph> @iamajmalhassan what in particular? You sign a transaction before you propagate it through the network.
Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<carver> @iamajmalhassan are you using a node with hosted keys, or do you have local private keys? If you're using hosted keys, you don't have to worry about signing a transaction at all. Some more background: https://web3py.readthedocs.io/en/stable/web3.eth.account.html#local-vs-hosted-nodes
Voith Mascarenhas
@voith

thanks for jumping back in! no issue yet, feel free to create one if you want to solicit more thoughts from the team.

I have some working code, I’ll create a PR tomorrow. However, the are some issues with ganache and its best to show these through code rather than creating an issue.

Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<Marc Garreau (wolovim)> Thats great! Look forward to it.
LIZHOUYI
@LIZHOUYI
taiyi
manuthema-rodriguez
@manuthema-rodriguez
Hello!! thanks @marcgarreau !