Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 17:34
    mortelli commented #1892
  • 16:00

    janos on pushsync-pusher

    (compare)

  • 16:00

    janos on master

    pushsync: split sync to chunksW… (compare)

  • 16:00
    janos closed #1881
  • 15:12
    ralph-pichler synchronize #1887
  • 15:12

    ralph-pichler on swap-pending-cheques

    swap: introduce pending cheques… swap: return if confirm while n… swap: add comments for pending … and 2 more (compare)

  • 14:25
    nonsense review_requested #1881
  • 14:23
    janos synchronize #1881
  • 14:23

    janos on pushsync-pusher

    pushsync: call FinishRootSpan o… (compare)

  • 14:16
    janos commented #1881
  • 14:15
    janos unlabeled #1881
  • 14:15
    janos labeled #1881
  • 14:14
    nonsense commented #1881
  • 14:12
    janos synchronize #1881
  • 14:12

    janos on pushsync-pusher

    pushsync: remove commented code (compare)

  • 14:11
    nonsense commented #1903
  • 14:10
    janos synchronize #1881
  • 14:10

    janos on pushsync-pusher

    network: Reconnect to the same … testutil: remove pre Go 1.13 su… build: configure golangci-lint … and 11 more (compare)

  • 14:09
    nonsense labeled #1903
  • 14:09
    nonsense opened #1903
swarm team
@ethswarm_gitlab
[mattermost] <lash> @Amxx yes of course, in fact if you have only one eth address in your geth wallet merely running swarm should do, if not then swarm --bzzaccount <key>
[mattermost] <lash> It's all in the (RTF)M https://swarm-guide.readthedocs.io/en/latest/node_operator.html
Hadrien Croubois
@Amxx
I feel like mixing http and bzz would be a terrible idea ... I want to point at ressources from th ENS ... i already have ipfs://Qm.... supported, I'd like to do the same for swarm. Obviously hardcoding http://something/bzz-raw:/somehash would be a terrible idea
I need an eth account to push to swarm ?
swarm team
@ethswarm_gitlab

[mattermost] <lash> > I need an eth account to push to swarm ?

you need one to run a node

Hadrien Croubois
@Amxx
does it need eth ?
swarm team
@ethswarm_gitlab
[mattermost] <lash> nono
[mattermost] <lash> It's just the key you need
[mattermost] <lash> I have a script to generate a wallet without geth if you need
[mattermost] <lash> You can find it in the AUR archlinux package: https://aur.archlinux.org/packages/go-swarm
Hadrien Croubois
@Amxx
If I don't provide one, shouldn't swarm generate a disposable one ? I mean, what will this wallet be used for, does it control access/edit to the data I push ?
swarm team
@ethswarm_gitlab
[mattermost] <lash> Hm maybe even it does now
Hadrien Croubois
@Amxx
I'l have a look at go-swarm
swarm team
@ethswarm_gitlab
[mattermost] <lash> apparently not:
$ dir=mktemp
$ swarm --datadir $dir
INFO [08-26|14:23:57.494] Maximum peer count                       ETH=25 LES=0 total=25
Fatal: bzzaccount option is required but not set; check your config file, command line or environment variables
Hadrien Croubois
@Amxx
btw, if go-swarm is the way to go, you should move it out of AUR into community. sysadmin generaly don't like AUR packages on prod servers
swarm team
@ethswarm_gitlab
[mattermost] <lash> @Amxx the package is one week old
[mattermost] <lash> And not vetted in any way
[mattermost] <lash> And my private initiative - not an "official" package
Hadrien Croubois
@Amxx
the AUR's go-swarm package doesn't compile because PGP keys cannot be verified
swarm team
@ethswarm_gitlab
[mattermost] <lash> README :)
Hadrien Croubois
@Amxx
(unknown public key 93EC1C676274C889)
swarm team
@ethswarm_gitlab
[mattermost] <lash> You don't like reading much today, do you? ;)
[mattermost] <lash> > 404 - Page Not Found
Sorry, the page you've requested does not exist.
Note: Git clone URLs are not meant to be opened in a browser.
Hadrien Croubois
@Amxx
I'm exhausted from ETHBerin and a long flight :)
I was looking for a README
swarm team
@ethswarm_gitlab
[mattermost] <lash> oh maybe I forgot to push it
[mattermost] <lash> indeed!
Hadrien Croubois
@Amxx
I don't know were to look for it, this is why I was looking for a github on the aur package page
swarm team
@ethswarm_gitlab
[mattermost] <lash> Thanks I'll push it now
[mattermost] <lash> anyway run gpg --recv-keys 0826EDA1702D1E87C6E2875121D2E7BB88C2A746 first
Hadrien Croubois
@Amxx
I think I'll just use the dappnode module and forget about it
that probably the best UX I'm going to have

Dappnode tells me:

Can't download swarm.dnp.dappnode.eth image: Ipfs hash not available: Qmb6d1QTzDMMR5nTPrRTHd3Y27mwP9dCAMTa8zzFJen1M1

I don't know if this is sad or funny
a bit of both I guess
swarm team
@ethswarm_gitlab

[mattermost] <lash> > dappnode module

when is it from?

bonhardt
@bonhardt
hey, i see some contract on etherscan have swarm hash, i tried few but none of them working. what do i miss ?
swarm team
@ethswarm_gitlab
[mattermost] <aron> @bonhardt - you missed nothing. etherscan publishes the hash (and maybe even the old, redundant format of swarm hash) but that is all. If the contract was never uploaded to swarm, knowing its hash will not help much.
[mattermost] <aron> I think of it as a placeholder for future swarm links :)
swarm team
@ethswarm_gitlab

[mattermost] <agazso> I have a question regarding Swarm Feeds
I'm creating ad-hoc feeds for connection initiation. This means that I generate random addresses with the appropriate keys and write to feed, then send the address to someone else who reads the information from the feed.
Most of the time feeds are written once. Now I'm using the API as it's written in the documentation [1], and it works on my private Swarm network. My problem is that getting the feed template can take up to 5 seconds, because (AFAIK) it tries to lookup the previous value, but I know that's empty because the feed address was just randomly generated.
So my question is how can I avoid getting the initial feed template? I also tried to generate the epoch part of the feed template with different values based on the code, but it was not really deteriministic if it could find the values or not after that.

1

swarm team
@ethswarm_gitlab
[mattermost] <nagydani> Guys, where is the office hours this week?
Scott Stevenson
@tenfinney

I just loaded v5. looks great! RE: ENS support:
On this machine I have run several Ethereum clients that have been/are located in /.geth /.ethereum and /.parity directories.
Currently my EVM live local node is a Parity Docker image running in /.parity directory. Each time I start the Docker Swarm with ENS it creates a NEW account so I assume swarm is confused where to look for the keystore file:
Question 1: Where should Swarm be looking for that keystore file that is created?
It's not in any of the 3 locations mentioned above?

I know I should probably purge all non running chains but in the meantime I might be able to continue as long as I can locate the keystore file location so Swarm does not need to generate a new keystore file each time.

Other than a new keystore file being created each time I start the Docker Swarm image with ENS api, everything else is running perfectly! Great work!

swarm team
@ethswarm_gitlab
[mattermost] <aron> Swarm takes a --datadir directive. perhaps that helps.
otherwise I believe it uses .ethereum/swarm
Scott Stevenson
@tenfinney

OK. It looks like it is a dynamic process. Every time I stop the Swarm Docker image, and then restart, it generates a new hidden .ethereum directory under the root at

/var/lib/docker/overlay2/bf1ec1554c98b19c5413406488e8f3094851f78e422c212745a66cf37d66b819/diff/root/.ethereum/swarm

where the /bf1ec...b1819/ changes every time I restart.

If this is the proper function; how does that affect the new SWAP: A first version of of the SWarm Accounting Protocol (SWAP) is implemented. SWAP is a tit-for-tat incentive system where nodes account how much data they request and serve to their peers.

Is the "accounting" not going to be tied the the keystore file? And if so, if that changes at every startup won't that make accounting difficult?

Once a node is up and running, I expect that not to make much difference because the node should preferably NEVER go down.

But in the meantime, for testing should I just accept the regenerated directory and new keystore file each time?

swarm team
@ethswarm_gitlab
[mattermost] <aron> I suggest you persist the keystore and chunkstore (datadir) between restarts. Otherwise you have to start again from zero every time.
ether9
@ether9
Are there any cool projects using Swarm at the moment
?
Nick Savers
@nicksavers
@ether9 Trinity uses it now
Attila Gazso
@agazso
@ether9 check out Felfele, a social mobile app built on Swarm
https://github.com/felfele/felfele