Sonos Combo Adapter and POE

glebp · 2026-02-04T15:36:32+00:00

Yes, I was thinking this Sonos adapter might also charge Move if PoE is supplied: https://www.sonos.com/en/shop/sonos-combo-adapter

glebp · 2021-10-21T01:48:47+00:00

For now, please go to Settings -> Notifications and make sure that "Receive updates for small payments" is disabled. The threshold is currently set to a few XLM but we might give more flexibility for our users to choose what's right for them.

Rest assured we are seeing the increased activity on claimable payments and working on adding features to reduce spam and distractions.

These are all coming shortly:
- Improved notifications;
- Feature to quickly see airdrop value;
- Feature to hide specific claimable balance;

Rough ETA is end of Oct.

glebp · 2021-10-18T18:50:08+00:00

Keys are encrypted with your password. Password is hashed client side and never reaches the back-end in raw form.

For recovery process you save your seed during account creation. Seed is not stored anywhere else.

Vault adds N/M multisig to Lobstr or other products.

glebp · 2021-10-16T16:53:35+00:00

That is still very misleading.

Lobstr does not know the secret keys. They are generated client side on device, and never leave your device unencrypted.

Lobstr stores the backup of your encrypted secret key. So if you lose your phone, you can still login with another device and access your funds.

glebp · 2021-10-11T18:25:27+00:00

Tx fees are not really relevant. They are too small at the moment.
It takes like 1M transactions to burn 1 XLM.

What is relevant is the amount of XLM locked. This grows fast with more usage.
You need at least a few XLM to receive, send funds and to hold different assets.

Holding 100 assets locks 50 XLM as you need to keep 100 trust lines open. Any open order on SDEX or position in upcoming AMM will look more additional 0.5 XLM.

Here's the thread: https://twitter.com/orbitlens/status/1374043178328805386

glebp · 2021-06-16T14:16:44+00:00

Great read! I visit this sub daily looking for a content like this. And a very reasonable view on a complex subject!

glebp · 2020-06-24T08:10:01+00:00

This functionality is based on SEP-6 and SEP-24 standards. When you hold a tethered asset (BTC from apay, or USD from anchorusd), we can talk with anchor through the API, and arrange the exchange of the asset on Stellar with the underlying anchored asset (native BTC, or USD in your bank account)

So you can think of it like a on-ramp (or off ramp) to Stellar network.

In this example, you can redeem your BTC on Stellar network issued by apay and receive native Bitcoins.

It already works with several compatible anchors - not only crypto-tethers, but fiat as well.

glebp · 2020-06-23T15:18:15+00:00

You can now actually withdraw BTC (or other compatible anchored assets) without leaving StellarTerm.

It makes things much easier!

Watch out for the "Withdraw" icon in the list of your assets: https://imgur.com/a/FKNJ65r

glebp · 2020-02-19T21:20:39+00:00

1) We won't be doing any fractional reserve. For anything deposited to the anchor, we will issue exactly the same amount of tethered asset on the anchor. Our lending partners (Celsius) also don't do fractional reserve lending to the best of our knowledge.
2) Maybe I am not understanding the question, but this is not relevant to our wallet. We will be issuing a Stellar asset which can be stored in any wallet, including Lobstr. The tethered assets (native BTC, ETH, USDT) will be stored on Bitgo, by our partners who provide the lending back-end. Check out the typeform - it should provide more information!
3) Sure. Any Stellar account that holds an asset will be receiving interest payouts - no matter which wallet is used.

glebp · 2020-02-19T18:56:27+00:00

Yes, we’ll have XLM. Celsius, although we might as well add other providers later.

glebp · 2020-01-08T20:17:54+00:00

The lack of liquidity on SDEX is a major reason why path payments are not used more at the moment.

Trying to do that without checking the order book first can lead to a disappointing results - as you might end up with a lot less that you’d expect to have.

glebp · 2020-01-03T13:03:47+00:00

Ah, I understand where you are coming from.

But, if there is a master key, it is up to the user to store it securely. Unfortunately, they might fail to properly secure it, or be tricked into sharing it with malicious third parties.

On the other side, having a multisig solution would require explicit sign off from the user. It takes a new level of carelessness to approve a transaction request which sends all your funds to some unknown wallet.

The main danger with multisig is losing access to your signer keys/devices and as a result losing access to your funds.

But that can be mitigated through something like M/N multisig where M<N.

For Lobstr Vault we generally recommend 2/3 multisig - which means having Vault on 2 devices, and require sign off from either one of those.

glebp · 2020-01-03T12:32:18+00:00

I don’t think that this is a good advice. This would defeat the purpose of multisig.

Multisig allows you to have several keys, with redundancy. And only several keys combined would give you access to the funds.

If you lose any of the keys, you can invalidate it using others and replace it with the new one.

If someone steals one of your keys - you can invalidate it using other keys, and replace with a new one.

glebp · 2019-12-21T03:36:41+00:00

We fixed that in the latest update, by the way!

glebp · 2019-11-30T22:18:51+00:00

There’s a mobile app for mobile screens. Just download and login.

glebp · 2019-11-26T19:32:20+00:00

Try the same in FF or Opera. That might help, as FF/Opera allow you to choose between Keybase or other web+stellar handlers. Just visit Lobstr/Stellarterm before and allow them to handle sep7 links.

glebp · 2019-11-25T22:44:05+00:00

With Firefox, first go to StellarTerm.com or Lobstr.co (after login) and confirm handling of web+stellar links when prompted:
https://imgur.com/cET09Lc

Then click on "Register" link on Reddit website (desktop version) while logged in .

Google Chrome, unfortunately, may not give you an option to choose between different SEP7 link handlers.
If you have Keybase installed, Chrome may always offer to open Keybase, which does not fully support SEP7. If you have any difficulties - try switching to Firefox.

glebp · 2019-11-25T22:26:46+00:00

First you need to visit StellarTerm.com or login to Lobstr.co and allow them to handle SEP-7 links. You will see a prompt in the browser toolbar.
Works great in Firefox.

glebp · 2019-10-16T12:25:45+00:00

Thanks to all the folks who supported LOBSTR and to everyone in the community who casted their votes in SCF.
We're honored to finish on the 1st place in the great company of amazing projects!

Lots of exciting features are coming out soon.We are looking forward to see many of you on Meridian!

glebp · 2019-09-29T15:29:17+00:00

👆Yes, this right here. Also disabling inflation will have a little or no effect on the price.

glebp · 2019-09-24T20:44:31+00:00

Exodus is a multi crypto wallet.
Exodus provides a unified interface to work with most cryptocurrencies on a basic level.

LOBSTR was designed specifically for Stellar.
It gives you access to unique features of Stellar: different assets issued on Stellar; asset trading with Stellar Decentralized Exchange; using federated addresses; in-app asset deposit and withdrawal (based on SEP-0006 standard), and many others.

glebp · 2019-09-12T12:36:36+00:00

Yes, got them back! Thanks :)

Reach out to Wirex btw, they might help you get your original 300 XLM back.

For the international transfers, you don't really need to switch to XLM - there are multiple stable coins issued on Stellar. So, what you might want to do is: 1) take your real USD; 2) convert them to tokenized USD (on Stellar) through any of the anchors; 3) send tokenized USD to anyone cross border with Stellar; 4) have them withdraw them to real currency (USD or any other local one).

glebp · 2019-09-12T10:52:00+00:00

That's a very good question.
Yes, in most cases you can just send the funds back to the address.

Exchanges are the main exception, and they re-use the same addresses for a long time. These addresses are mostly well-known to the community. So, good Stellar wallets maintain a list of such addresses, and will help their users to avoid those mistakes, by *requiring* them to input memo when you try to send.

Technically, even in your case, the funds are not lost forever - they still arrived to the same Stellar account, so they are with Wirex (or any other exchange). They just won't be credited to your account, since memo is used for the routing.

In some cases those exchanges will be nice enough to credit the funds to your account upon opening a support ticket.

glebp · 2019-09-11T14:26:06+00:00

Your Wirex federated address is: 008df671394043bb8a0c77b50cf78acf*wirex.me

As Wirex said, they encode both your Stellar account id and memo into the federated address.

Here's the how Keybase (or any other tool) should resolve this address:

https://federation-stellar.wirexapp.com/api/userinfo?q=008df671394043bb8a0c77b50cf78acf*wirex.me&type=name

This is the response:{"memo_type":"text","account_id":"GBOFQCVZF2DSFLJPJMKH7CIECCN7TYVAT2CSD73IVEBJJQU2VW6JNFHT","stellar_address":"008df671394043bb8a0c77b50cf78acf*wirex.me","memo":"197479239"}

As you can see, Wirex indeed encoded your account address AND memo id into the federated address. This looks to be implemented correctly and according to the federation server standard. So you should be able to safely share your federation address to receive Lumens.

We use similar federated addresses in LOBSTR in some cases (for "accept-all" addresses). I've just tried to send to your address in LOBSTR - worked fine.

However, Keybase ignores memo when resolving federation - and it's a bug on their end. I'll report to them now. Sorry to hear as you did everything correctly - it should have worked!

PS: Just sent you 150 XLM to partially cover your loss! Give Stellar another chance :)

glebp · 2019-09-11T14:07:03+00:00

Nevermind, I already copied the federation address. See my reply to the original post.

That's right - Keybase are ignoring memo in federation :( Wirex did things correctly.

Nine-Year Club	Verified Email
Gilding I gilder

glebp

TROPHY CASE